Reflective qos flow characteristic-based communications method and apparatus

ABSTRACT

This application provides a reflective QoS flow characteristic-based communications method and apparatus. In the method, an access-network network element sends first information to a core-network network element, where the first information is used to indicate whether a data packet has a reflective QoS flow characteristic; and the access-network network element determines, based on the first information, whether there is a need to send a QoS flow identifier to a terminal. In this way, signaling overheads are reduced.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/566,638, filed on Sep. 10, 2019, which is a continuation ofInternational Application No. PCT/CN2018/085867, filed on May 7, 2018,which claims priority to Chinese Patent Application No. 201710313900.5,filed on May 5, 2017 and to Chinese Patent Application No.201710458757.9, filed on Jun. 16, 2017, All of the afore-mentionedpatent applications are hereby incorporated by reference in theirentireties.

TECHNICAL FIELD

This application relates to the field of communications technologies,and in particular, to a reflective QoS flow characteristic-basedcommunications method and apparatus.

BACKGROUND

In a next-generation communications system, a flow-based quality ofservice (QoS) architecture is proposed.

The flow-based QoS architecture mainly includes quality of service flow(QoS flow) mapping in a non-access stratum (NAS) and an access stratum(AS). QoS flows are data flows in a packet data unit (PDU) session thathave a same QoS requirement, and may also be understood as a pluralityof Internet Protocol (IP) flows that have a same QoS requirement or agroup of data packets of another type that have a same QoS requirement.The NAS layer is mainly responsible for a mapping relationship between aQoS flow and an IP flow or another type of data packets. A core networkuser plane function (UPF) generates a downlink QoS flow, and a terminalgenerates an uplink QoS flow. The AS layer is mainly responsible for amapping relationship between a QoS flow and a data radio bearer (DRB). Anetwork side (such as a base station) configures the mappingrelationship between a QoS flow and a DRB, and provides, in anair-interface DRB, a QoS service for a QoS flow.

In a fifth-generation communications system (5G), a reflective QoScharacteristic is further introduced into the flow-based QoSarchitecture. The reflective QoS characteristic means that a QoS flow issymmetrical in terms of uplink and downlink. To be specific, QoS of anuplink flow is the same as QoS of a downlink flow, and an uplink packetfiltering template and a downlink packet filtering template are alsosymmetrical. For example, an uplink source address is a downlinkdestination address, an uplink source port number is a downlinkdestination port number, an uplink destination address is a downlinksource address, and an uplink destination port number is a downlinksource port number.

In a reflective QoS characteristic-based communication process, to savecontrol signaling, the network side does not notify, by using signaling,a terminal of a rule for mapping an uplink IP flow or another type ofdata packets to a QoS flow, but implicitly notifies the terminal of therule by using a downlink data packet. After receiving a downlink datapacket having the reflective QoS characteristic, the terminal reversesan information quintuple in a header of the downlink data packet toobtain an uplink packet filter. In addition, a QoS parameter index valuecorresponding to the uplink packet filter is a QoS parameter index valuecarried in the header of the downlink packet. Therefore, the terminalcan obtain uplink QoS information such as a packet filter and a QoS flowidentifier (id) without receiving a NAS signaling notification.

In the foregoing manner, although the terminal can receive controlsignaling, the terminal needs to detect header information of eachreceived downlink data packet, so as to determine whether the receiveddownlink data packet has the reflective QoS characteristic. However, inthe 5G communications system, a data transmission rate is extremelyhigh, and if the terminal detects each downlink data packet, extremelylarge overheads are caused, affecting performance and power consumptionof the terminal.

SUMMARY

Embodiments of this application provide a reflective QoS flowcharacteristic-based communications method and apparatus to reducesignaling overheads.

According to a first aspect, a reflective QoS flow characteristic-basedcommunications method is provided. In the method, an access-networknetwork element determines whether there is a need to send a QoS flowidentifier (QoS flow ID) to a terminal. The access-network networkelement sends a QoS flow ID to the terminal when determining that thereis a need to send the QoS flow ID to the terminal, or the access-networknetwork element does not send a QoS flow ID when there is no need tosend the QoS flow ID, so as to save signaling overheads.

In a possible design, a core-network network element sends firstinformation to the access-network network element, where the firstinformation is used to indicate whether a data packet has a reflectiveQoS characteristic. The access-network network element receives thefirst information sent by the core-network network element, anddetermines, based on the first information, whether there is a need tosend a QoS flow ID to the terminal. The access-network network elementmay further send first indication information to the terminal, where thefirst indication information is used to indicate whether the terminalneeds to read a QoS flow ID.

The core-network network element may be a core network control planenetwork element, such as an AMF. The access-network network element maybe a base station, such as a gNB.

If a data packet has the reflective QoS characteristic, this means thatthe terminal can obtain an uplink QoS flow ID and packet filter based onthe data packet in a reflective manner. If a data packet does not havethe reflective QoS characteristic, this means that the terminal cannotobtain an uplink QoS flow ID and an uplink packet filter based on thedata packet in a reflective manner.

In another possible design, the first information is further used toindicate a reflective QoS type of a data packet. The reflective QoS typeof a data packet includes: all data packets have the reflective QoScharacteristic, some data packets have the reflective QoScharacteristic, or none of data packets have the reflective QoScharacteristic.

The access-network network element may determine, based on the firstinformation, whether a data packet has the reflective QoScharacteristic, and determine, based on the reflective QoS type of adata packet, whether all data packets have the reflective QoScharacteristic, some data packets have the QoS reflective QoScharacteristic, or none of data packets have the reflective QoScharacteristic. The access-network network element may also determine,based on the reflective QoS type of a data packet, whether a data packethas the reflective QoS characteristic.

In still another possible design, the first information may bereflective QoS information sent by the core network control planenetwork element, and the reflective QoS information is used to indicatewhether a data packet has the reflective QoS characteristic. The corenetwork control plane network element sends the reflective QoSinformation to the access-network network element. The access-networknetwork element receives the reflective QoS information sent by the corenetwork control plane network element, and determines, based on thereflective QoS information sent by the core network control planenetwork element, whether there is a need to send a QoS flow ID to theterminal.

When determining that a data packet has the reflective QoScharacteristic, the access-network network element determines that thereis a need to send a QoS flow ID to the terminal; or when determiningthat a data packet does not have the reflective QoS characteristic, theaccess-network network element determines that there is no need to senda QoS flow ID to the terminal, so as to save signaling overheads.

The reflective QoS information may be reflective QoS information of aQoS flow, or may be reflective QoS information of a PDU session.

In still another possible design, the core network control plane networkelement may further send reflective QoS information update indicationinformation to the access-network network element, and the reflectiveQoS information update indication information is used to instruct theaccess-network network element device to update the received reflectiveQoS information.

In still another possible design, the access-network network element maydetermine a mapping relationship between a QoS flow and a DRB based onreflective QoS information of a QoS flow or a PDU session, for example,the access-network network element may map QoS flows that differ in thereflective QoS characteristic to different DRBs.

In still another possible design, the first indication information maybe reflective QoS information sent by the access-network network elementto the terminal. The access-network network element sends the reflectiveQoS information to the terminal. The terminal receives the reflectiveQoS information sent by the access-network network element, anddetermines, based on the reflective QoS information, whether there is aneed to read a QoS flow ID.

The reflective QoS information sent by the access-network networkelement to the terminal may be reflective QoS information of a QoS flow,reflective QoS information of a DRB, or reflective QoS information of aPDU session (or an SDAP entity).

For a DRB, an SDAP entity, or a QoS flow that includes a data packethaving the reflective QoS characteristic, the terminal detects a QoSflow ID and a data packet header, and generates an uplink QoS flow IDand a corresponding packet filter based on the detected QoS flow ID.However, for a DRB, an SDAP entity, or a QoS flow of a data packet thatdoes not have the reflective QoS characteristic, the terminal may notdetect a QoS flow ID and a data packet header, so as to save signalingoverheads of the terminal.

In still another possible design, the first information may be areflective QoS flow characteristic indicator (RQI) sent by a corenetwork user plane network element, and the RQI is used to indicate thatsome data packets have the reflective QoS flow characteristic.

The core-network network element may not send the reflective QoScharacteristic of a QoS flow to the access-network network element.After the access-network network element obtains an RQI by parsing aheader of a data packet to be sent through an N3 interface, theaccess-network network element determines that the QoS flow has thereflective QoS characteristic and that some data packets have thereflective QoS characteristic, where the RQI is used to indicate that adata packet has the reflective QoS characteristic. Alternatively, for aQoS flow whose QoS parameter is standardized, the access-network networkelement may consider by default that the QoS flow has the reflective QoScharacteristic and that some data packets have the reflective QoScharacteristic.

In still another possible design, the core-network network element maysend reflective QoS information deactivation indication information tothe access-network network element. The reflective QoS informationdeactivation indication information is used to indicate reflective QoSdeactivation information. The reflective QoS deactivation informationmeans that a data packet having the reflective QoS characteristic asindicated by the reflective QoS information does not have the reflectiveQoS characteristic any longer. The access-network network elementreceives the reflective QoS information deactivation indicationinformation sent by the core-network network element, deactivates thereflective QoS characteristic of a data packet based on the reflectiveQoS information deactivation indication information, and determines thatthere is no need to send a QoS flow ID for a data packet whosereflective QoS characteristic has been deactivated.

The reflective QoS deactivation information that the reflective QoSinformation deactivation indication information sent by the core-networknetwork element to the access-network network element indicates may bereflective QoS deactivation information of a QoS flow, or may bereflective QoS deactivation information of a PDU session.

The reflective QoS information deactivation indication information maybe used to indicate deactivation of the reflective QoS characteristicfor one or more QoS flows or PDU sessions.

In still another possible design, the access-network network element maysend reflective QoS information deactivation indication information tothe terminal. Reflective QoS deactivation information that thereflective QoS information deactivation indication information sent bythe access-network network element to the terminal indicates may be notonly reflective QoS deactivation information of a QoS flow or a PDUsession, but also reflective QoS deactivation information of a DRB. Theterminal receives the reflective QoS information deactivation indicationinformation sent by the access-network network element, and determinesthat there is no need to read a QoS flow ID of a data packet that doesnot have the reflective QoS characteristic any longer, so as to savesignaling overheads.

In still another possible design, a decompression operation performed ata PDCP layer at a receive end of the terminal for robust headercompression (ROHC) may be used to directly decompress a PDCP SDU fromwhich a PDCP header is removed, and there is no need to perform anoperation caused by an SDAP header, such as an initial decompressionlocation offset operation, so that signaling overheads are saved.

In this embodiment of this application, the access-network networkelement notifies the terminal of reflective QoS information of a QoSflow, a DRB, or a PDU session, and may deactivate the reflective QoScharacteristic of a QoS flow, a DRB, or a PDU session. The terminal maydetermine, based on the reflective QoS information, whether there is aneed to read a QoS flow ID through an air interface and whether there isa need to perform an ROHC location offset operation. For a DRB that doesnot have the reflective QoS, the terminal does not detect a QoS flow ID,and does not perform an ROHC decompression location offset operation, soas to reduce detection work performed by the terminal for anair-interface data packet and reduce overheads, thereby improvingprocessing efficiency and saving power.

In still another possible design, if cell handover for the terminaloccurs, a source access-network network element (a source base station)that obtains the first information (the reflective QoS information) maysend the obtained reflective QoS information to a target access-networknetwork element (a target base station) to which the terminal is to behanded over, and the target access-network network element decides toperform one or more of the following operations: sending a QoS flow IDthrough the air interface, configuring whether the terminal needs toread a QoS flow ID, configuring, for the terminal, a manner ofconfiguring a mapping relationship between a QoS flow and a DRB,deciding whether to configure an SDAP entity for a PDU session, and soon.

In still another possible design, the core-network network element mayfurther send a QoS rule validity time to the access-network networkelement, and a QoS rule is effective in the QoS rule validity time. Theaccess-network network element may send the QoS rule validity time tothe terminal after receiving the QoS rule validity time, so that theterminal maps, in the QoS rule validity time by using a same QoS rule,data packets having the reflective QoS characteristic into a QoS flow.

The QoS rule validity time sent by the core-network network element tothe access-network network element may be an effective reflective QoSrule validity time of a QoS flow, or may be an effective reflective QoSrule validity time of a PDU session.

In still another possible design, the core-network network element mayfurther send QoS rule validity time update information to theaccess-network network element, and the QoS rule validity time updateinformation is used to indicate an updated QoS rule validity time.

In still another possible design, if the access-network network elementreceives, in the QoS rule validity time, at least two data packetshaving the reflective QoS characteristic, the access-network networkelement may send, for some of the at least two data packets in the QoSrule validity time, the first information used to indicate whether adata packet has the reflective QoS characteristic, so as to filter thefirst information to be sent, thereby saving signaling overheads.

In still another possible design, the source access-network networkelement (the source base station) may send a QoS rule validity time of adata packet of a to-be-switched QoS flow to the target access-networknetwork element (the target base station) to which the terminal is to behanded over. The target access-network network element may filter, basedon the QoS rule validity time, the reflective QoS information to be sentto the terminal, so as to filter the reflective QoS information to besent to the terminal, thereby saving signaling overheads.

The target access-network network element may ignore the QoS rulevalidity time of the data packet sent by the source access-networknetwork element, so as to avoid QoS rule validity time synchronizationbetween the source access-network network element and the targetaccess-network network element.

The QoS rule validity time that may be sent by the source access-networknetwork element to the target access-network network element to whichthe terminal is to be handed over may be a QoS rule validity time of aQoS flow, or may be a QoS rule validity time of a PDU session.

In still another possible design, a data packet of a QoS flow istransmitted by using a non-transparent-mode SDAP frame format or byusing a transparent-mode SDAP frame format.

The transparent-mode SDAP frame format means that no SDAP header isconfigured for a DRB. In other words, an SDAP PDU does not include SDAPheader. The non-transparent-mode SDAP frame format means that an SDAPheader is configured for a DRB. In other words, an SDAP PDU includes theSDAP header.

In the non-transparent-mode SDAP frame format, if a bit used to indicatean NRQI and a bit used to indicate an ARQI both are set to 0, the SDAPheader may not carry a QFI field. If at least one of the bit used toindicate the NRQI or the bit used to indicate the ARQI is set to 1, theSDAP header carries the QFI field.

In a data transmission process, an SDAP entity at a data receive endreceives a PDCP SDU from a PDCP layer, and reads the SDAP header. If avalue of the bit used to indicate the NRQI is 1, it indicates that thedata packet has the reflective QoS characteristic. In this case, theSDAP entity delivers, to an upper layer such as a NAS layer, a dataportion of SDAP and a QoS flow ID that is read from the SDAP header. Thedata portion and the QoS flow ID that are delivered to the upper layermay be used to generate a QoS rule at the upper layer. Further, the SDAPentity may send the NRQI to the upper layer.

In the non-transparent-mode SDAP frame format, the SDAP header furtherincludes a bit used to indicate a URQI.

In the non-transparent-mode SDAP frame format, a bit is set in the SDAPheader, where the bit is used to indicate whether transmission, in acorresponding DRB, of a data packet of a QoS flow ends. For example, anEnd field is set.

In the non-transparent-mode SDAP frame format, a control command may beset in the SDAP header, where the control command is used to feed backcompletion of receiving, in a DRB, of a data packet of a QoS flow.

In still another possible design, an SDAP transparent mode may beunidirectionally set. The SDAP transparent mode is configured in adownlink direction of at least one DRB, or the SDAP transparent mode isconfigured in an uplink direction of at least one DRB.

In still another possible design, in a data transmission process, theaccess-network network element may send SDAP mode information to theterminal. The SDAP mode information is used to indicate whether an SDAPframe format is in a transparent mode or a non-transparent mode, andindicate a direction corresponding to an SDAP mode.

The source access-network network element (the source base station) maysend the SDAP mode information to the target access-network networkelement (the target base station) to which the terminal is to be handedover.

According to a second aspect, an access-network network element mayfilter a to-be-sent QoS flow ID. When determining that a header of adata packet to be sent to a terminal needs to carry a QoS flow ID, theQoS flow ID is included in the header of the data packet; or whendetermining that a header of a data packet to be sent to a terminal doesnot need to carry a QoS flow ID, the QoS flow ID is not included in theheader of the data packet, so as to decrease a quantity of QoS flow IDsto be sent through an air interface, thereby saving signaling overheads.

In a possible design, the access-network network element determines datapacket header information, and determines, based on the data packetheader information, whether there is a need to add a QoS flow ID to theheader of the data packet to be sent to the terminal.

In a possible design, a core-network network element sends reflectiveQoS information and packet filter composition information to theaccess-network network element. The packet filter compositioninformation may be packet filter composition information correspondingto a reflective QoS characteristic of a QoS flow or a PDU session. Forexample, the packet filter composition information may be an IPquintuple (a source address, a destination address, a source portnumber, a destination port number, and a protocol number), or a MediaAccess Control (MAC) source address or an MAC destination address.

The access-network network element receives the reflective QoSinformation and the packet filter composition information that are sentby the core-network network element. The access-network network elementdetermines, based on the corresponding packet filter compositioninformation in the header of the data packet, whether there is a need toadd a QoS flow ID to the header of the data packet to be sent to theterminal. For example, the access-network network element detects aheader of each received data packet of a QoS flow based on packet filtercomposition. If a part that is in the header of the data packet andcorresponds to a packet filter is new content, a QoS flow ID is carriedin the data packet to be sent through an air interface. If the part thatis in the header of the data packet and corresponds to the packet filteris not new, a QoS flow ID is not carried in the data packet to be sentthrough an air interface.

Further, the access-network network element may also determine whetherthere is a need to add, to the header of the data packet to be sent tothe terminal, indication information used to indicate that the datapacket has a reflective QoS characteristic. For example, theaccess-network network element detects a header of each received datapacket of a QoS flow based on packet filter composition. If the partthat is in the header of the data packet and corresponds to the packetfilter is new content, the indication information may be further carriedto indicate that the data packet has the reflective QoS characteristic.If the part that is in the header of the data packet and corresponds toa packet filter is not new, the indication information used to indicatethat the data packet has the reflective QoS characteristic is notcarried.

In another possible design, if the access-network network elementdetermines that there is a need to add a QoS flow ID to the header ofthe data packet to be sent to the terminal, the access-network networkelement sends a user plane control PDU (such as an SDAP control PDU or aPDCP control PDU) or RRC signaling (including but not limited to an RRCconfiguration message, an RRC reconfiguration message, or the like) tothe terminal. The user plane control PDU and the RRC signaling bothinclude a QoS flow ID of the data packet and header information of thedata packet.

In still another possible design, if the access-network network elementdetermines that there is a need to add a QoS flow ID to the header ofthe data packet to be sent to the terminal, the access-network networkelement performs, based on the packet filter composition information, areflective operation on content that is in the header of the data packetand corresponds to the packet filter composition information, so as toobtain an uplink packet filter. The access-network network element sendsthe uplink packet filter and the QoS flow ID to the terminal, and theterminal receives the QoS flow ID and the corresponding uplink packetfilter to generate an uplink QoS flow.

In still another possible design, the terminal may send first capabilityinformation to the access-network network element; or the access-networknetwork element may send first capability information to thecore-network network element, and the core-network network elementreceives the first capability information and sends the first capabilityinformation to the access-network network element. The first capabilityinformation is used to indicate whether the terminal has at least one ofa capability of reading a QoS flow ID and a capability of generating anuplink packet filter. The capability of reading a QoS flow ID is acapability of obtaining, by the terminal, a QoS flow ID from a receivedair-interface data packet. The capability of generating an uplink packetfilter is a capability of generating, by the terminal, an uplink packetfilter based on a received downlink air-interface data packet. Theaccess-network network element receives the first capabilityinformation. If the access-network network element determines, based onthe first capability information, that a capability or a status of theterminal does not support reading of a QoS flow ID and generating of anuplink packet filter, the access-network network element notifies, byusing a user plane control PDU or RRC signaling, the terminal of a QoSflow ID and an uplink packet filter corresponding to the QoS flow ID.The access-network network element may notify, by using the user planecontrol PDU or the RRC signaling, the terminal of the QoS flow ID andthe uplink packet filter corresponding to the QoS flow ID, so as toreduce overheads of the terminal and reduce overheads caused if the QoSflow ID is carried through an air interface.

In still another possible design, the terminal may further send secondcapability information to the access-network network element; or theterminal may send second capability information to the core-networknetwork element, and the core-network network element sends the secondcapability information to the access-network network element. The secondcapability information is used to indicate whether the terminal has areflective mapping capability. The reflective mapping capability is acapability of obtaining, by the terminal, a mapping relationship betweenan uplink QoS flow and a DRB based on a QoS flow ID carried in a headerof a downlink data packet. The access-network network element receivesthe second capability information sent by the terminal. If theaccess-network network element determines that the terminal does notsupport the reflective mapping capability, the access-network networkelement needs to configure, for the terminal in another manner, themapping relationship between an uplink QoS flow and a DRB, for example,configure the mapping relationship between an uplink QoS flow and a DRBby using RRC signaling.

According to a third aspect, a reflective QoS flow characteristic-basedcommunications apparatus is provided, and the reflective QoS flowcharacteristic-based communications apparatus has functions ofimplementing the access-network network element in the first aspect andthe second aspect. The functions may be implemented by using hardware,or may be implemented by executing corresponding software by hardware.The hardware or the software includes one or more modules correspondingto the foregoing functions. The module may be software and/or hardware.

In a possible design, the reflective QoS flow characteristic-basedcommunications apparatus includes a receiving unit and a processingunit, and may further include a transmitting unit. Functions of thereceiving unit, the processing unit, and the transmitting unit maycorrespond to the foregoing method steps. Details are not describedherein again.

According to a fourth aspect, a reflective QoS flow characteristic-basedcommunications apparatus is provided, and the reflective QoS flowcharacteristic-based communications apparatus has functions ofimplementing the core-network network element in the first aspect andthe second aspect. The functions may be implemented by using hardware,or may be implemented by executing corresponding software by hardware.The hardware or the software includes one or more modules correspondingto the foregoing functions. The module may be software and/or hardware.

In a possible design, the reflective QoS flow characteristic-basedcommunications apparatus includes a processing unit and a transmittingunit, and functions of the processing unit and the transmitting unit maycorrespond to the foregoing method steps. Details are not describedherein again.

According to a fifth aspect, a reflective QoS flow characteristic-basedcommunications apparatus is provided, and the reflective QoS flowcharacteristic-based communications apparatus has functions ofimplementing the terminal in the first aspect and the second aspect. Thefunctions may be implemented by using hardware, or may be implemented byexecuting corresponding software by hardware. The hardware or thesoftware includes one or more modules corresponding to the foregoingfunctions. The module may be software and/or hardware.

In a possible design, the reflective QoS flow characteristic-basedcommunications apparatus includes a receiving unit and a processingunit, and functions of the receiving unit and the processing unit maycorrespond to the foregoing method steps. Details are not describedherein again.

According to a sixth aspect, an access-network network element isprovided, and the access-network network element includes a processor, amemory, a bus system, a receiver, and a transmitter. The processor, thememory, the receiver, and the transmitter are connected to each other byusing the bus system. The memory is configured to store an instruction.The processor is configured to execute the instruction stored in thememory, to control the receiver to receive a signal and control thetransmitter to send a signal, so as to complete execution functions ofthe access-network network element in the first aspect, the secondaspect, and any possible design of the foregoing aspects.

According to a seventh aspect, a core-network network element isprovided, and the core-network network element includes a processor, amemory, a bus system, and a transmitter. The processor, the memory, andthe transmitter are connected to each other by using the bus system. Thememory is configured to store an instruction. The processor isconfigured to execute the instruction stored in the memory, to controlthe transmitter to send a signal, so as to complete execution functionsof the core-network network element in the first aspect, the secondaspect, and any possible design of the foregoing aspects.

According to an eighth aspect, a terminal is provided, and the terminalincludes a transmitter, a receiver, a processor, and a memory, and mayfurther include an antenna. The transmitter, the receiver, theprocessor, and the memory may be connected to each other by using thebus system. The memory is configured to store an instruction. Theprocessor is configured to execute the instruction stored in the memory,to control the receiver to receive a signal and control the transmitterto send a signal, so as to complete execution functions of the terminalin the first aspect, the second aspect, and any possible design of theforegoing aspects.

According to a ninth aspect, a communications system is provided,including the access-network network element in the sixth aspect, thecore-network network element in the seventh aspect, and one or moreterminals in the eighth aspect.

According to a tenth aspect, a computer storage medium is provided. Thecomputer storage medium is configured to store some instructions. Whenthese instructions are executed, any method related to the terminal, theaccess-network network element, or the core-network network element inthe first aspect, the second aspect, and any possible design of theforegoing aspects may be completed.

According to an eleventh aspect, a computer program product is provided.The computer program product is configured to store a computer program,and the computer program is used to perform the communications method inthe first aspect, the second aspect, and any possible design of theforegoing aspects.

In the embodiments of this application, the access-network networkelement determines whether there is a need to send a QoS flow ID to theterminal. The access-network network element sends a QoS flow ID to theterminal when determining that there is a need to send the QoS flow IDto the terminal, or the access-network network element does not send aQoS flow ID when there is no need to send the QoS flow ID, so as to savesignaling overheads. Further, the access-network network element mayfilter a to-be-sent QoS flow ID. A QoS flow ID is not included in aheader of a data packet to be sent to the terminal, when determiningthat there is a need to add the QoS flow ID to the header of the datapacket; or a QoS flow ID is included in a header of a data packet to besent to the terminal, when there is no need to add the QoS flow ID tothe header of the data packet, so as to save signaling overheads.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an architectural diagram of a communications system to whichan embodiment of this application is applicable;

FIG. 2 is a diagram of a QoS flow-based QoS architecture;

FIG. 3 is a schematic diagram of a process of mapping a QoS flow to aDRB;

FIG. 4 is a schematic diagram of a process of obtaining an uplink QoSflow ID and an uplink packet filter;

FIG. 5 is a schematic diagram of a process of mapping an uplink flow toa DRB;

FIG. 6 shows a reflective QoS characteristic-based communications methodaccording to an embodiment of this application;

FIG. 7 is a flowchart of an implementation method of a reflective QoScharacteristic-based communications method according to an embodiment ofthis application;

FIG. 8 is a flowchart of another implementation method of a reflectiveQoS characteristic-based communications method according to anembodiment of this application;

FIG. 9 is a flowchart of still another implementation method of areflective QoS characteristic-based communications method according toan embodiment of this application;

FIG. 10 is a flowchart of an implementation method for filtering a QoSflow ID according to an embodiment of this application;

FIG. 11 is a flowchart of another implementation method for filtering aQoS flow ID according to an embodiment of this application;

FIG. 12 is a flowchart of still another implementation method forfiltering a QoS flow ID according to an embodiment of this application;

FIG. 13 is a flowchart of still another implementation for filtering aQoS flow ID by an access-network network element according to anembodiment of this application;

FIG. 14 is a flowchart of yet another implementation method of areflective QoS characteristic-based communications method according toan embodiment of this application;

FIG. 15 is a schematic diagram of an SDAP frame format according to anembodiment of this application;

FIG. 16 is another schematic diagram of an SDAP frame format accordingto an embodiment of this application;

FIG. 17 is still another schematic diagram of an SDAP frame formataccording to an embodiment of this application;

FIG. 18 is yet another schematic diagram of an SDAP frame formataccording to an embodiment of this application;

FIG. 19 is still yet another schematic diagram of an SDAP frame formataccording to an embodiment of this application;

FIG. 20 is a schematic structural diagram of a reflective QoScharacteristic-based communications apparatus according to an embodimentof this application;

FIG. 21 is a schematic structural diagram of an access-network networkelement according to an embodiment of this application;

FIG. 22 is a schematic structural diagram of another reflective QoScharacteristic-based communications apparatus according to an embodimentof this application;

FIG. 23 is a schematic structural diagram of a core-network networkelement according to an embodiment of this application;

FIG. 24 is a schematic structural diagram of still another reflectiveQoS characteristic-based communications apparatus according to anembodiment of this application; and

FIG. 25 is a schematic structural diagram of a terminal according to anembodiment of this application.

DESCRIPTION OF EMBODIMENTS

The following describes the technical solutions in the embodiments ofthis application with reference to the accompanying drawings.

Some terms in this application are first explained and described tofacilitate understanding by a person skilled in the art.

(1). A base station (BS), which may also be referred to as a basestation device, is an apparatus deployed in a radio access network toprovide a wireless communications function. For example, in a 2Gnetwork, devices that provide a base station function include a basetransceiver station (BTS) and a base station controller (BSC). In a 3Gnetwork, devices that provide a base station function include a NodeBand a radio network controller (RNC). In a 4G network, devices thatprovide a base station function include an evolved NodeB (eNB). In awireless local area network (WLAN), a device that provides a basestation function is an access point (AP). In a future 5G new radio (NR),a device that provides a base station function includes a continuouslyevolved NodeB (gNB).

(2). A terminal is a device that provides voice and/or data connectivityfor a user, and may include a handheld device, an in-vehicle device, awearable device, or a computing device that has a wireless communicationfunction, or another processing device connected to a wireless modem,and user equipment (UE) in various forms, a mobile station (MS), aterminal device (Terminal Equipment), a transmission point (transmissionand receiver point (TRP); or transmission point (TP)), or the like.

(3). Exchange: “Exchange” in this application is a process in which twoexchanging parties transfer information to each other. The transferredinformation herein may be the same or different. For example, the twoexchanging parties are a base station 1 and a base station 2. The basestation 1 may request information from the base station 2, and the basestation 2 provides the information requested by the base station 1 tothe base station 1. Certainly, the base station 1 and the base station 2may request information from each other. The requested informationherein may be the same or different.

(4). “A plurality of” is two or more than two. The term “and/or”describes an association relationship for describing associated objectsand represents that three relationships may exist. For example, A and/orB may represent the following three cases: Only A exists, both A and Bexist, and only B exists. The character “/” usually indicates an “or”relationship between the associated objects.

(5). Terms “network” and “system” are usually interchangeably used, butmeanings of the terms can be understood by a person skilled in the art.Information, signal, message, and channel may be interchangeably usedsometimes. It should be pointed out that expressed meanings areconsistent when differences are not emphasized. “Of”, “relevant)”, and“corresponding” may be interchangeably used sometimes. It should bepointed out that expressed meanings are consistent when differences arenot emphasized.

(6). A protocol data unit (PDU) session may be understood as a link thatprovides a PDU link service between a terminal and a data network (DN).

(7). QoS flows are data flows in a PDU session that have a same QoSrequirement, and may be a plurality of IP flows having a same QoSrequirement.

(8). A data radio bearer (DRB) may be understood as a data bearerbetween a base station and a terminal. Data packets in the data bearerhave same forwarding processing.

(9). A DN is an external data network.

(10). A reflective QoS characteristic means that a QoS flow issymmetrical in terms of uplink and downlink. To be specific, uplink QoSis the same as downlink QoS, and an uplink packet filtering template anda downlink packet filtering template are also symmetrical. For example,an uplink source address is a downlink destination address, an uplinksource port number is a downlink destination port number, an uplinkdestination address is a downlink source address, and an uplinkdestination port number is a downlink source port number. A terminalobtains a packet filter of an uplink packet and a QoS flow ID of theuplink packet based on the reflective characteristic by using headerinformation of a downlink data packet.

The embodiments of this application provide a reflective QoScharacteristic-based communications method, and the method is applicableto a system with a QoS flow-based QoS architecture. For example, themethod is applicable to a scenario in which a terminal accesses afifth-generation core network (5G Core, 5GC) by using a next generationNodeB (gNB), including a scenario in which the terminal accesses thenetwork by using a single link, or accesses the network by using aplurality of links. For example, in a multi-connection scenario, theterminal accesses a 5G network by using a master gNB (MgNB) and asecondary gNB (SgNB).

In the embodiments of this application, a 5G network scenario in awireless communications network is used as an example below fordescription. It should be pointed out that the solutions in theembodiments of this application may be further applied to anotherwireless communications network, and a corresponding name may also bereplaced with a name of a corresponding function in the another wirelesscommunications network.

FIG. 1 is a schematic structural diagram of a communications system towhich this application is applicable. The communications system shown inFIG. 1 includes a next generation core network (NGC), also referred toas 5GC) and a next generation radio access network (NG-RAN). The 5GCmainly includes a user plane network element (UPF) and an access andmobility management function (AMF) of a control plane network element.The AMF is mainly responsible for access and mobility management for aterminal. The UPF is mainly responsible for IP address allocation andPDU session control and management for the terminal, and furtherincludes functions such as data packet routing and forwarding and QoSmanagement. A main network element included in the NG-RAN is a nextgeneration NodeB (gNB). The gNB provides a new radio (NR) control planeand a user plane protocol stack that are terminated at the terminal. Forexample, the gNB is responsible for functions such as access control,link management, measurement, dynamic resource allocation, and bearermanagement that are for the terminal, and is responsible for intra-celland inter-cell radio resource management (RRM) functions. Further, aninterface between control planes of the 5GC and the NG-RAN is an N2interface, an interface between user planes of the 5GC and the NG-RAN isan N3 interface, and an interface between gNBs is an Xn interface.

A QoS flow-based QoS architecture in a 5G scenario is shown in FIG. 2. Anon-access stratum service bearer corresponds to a QoS flow, and anaccess stratum service bearer corresponds to an air-interface radiobearer (RB) and a terrestrial tunnel (between the RAN and the 5GC). Thetunnel is established based on a PDU session. To be specific, QoS flowsbelonging to a same PDU session use a same tunnel. Each PDU session hasa unique identifier, and the unique identifier of the PDU session may beone of the following: a PDU session identifier, an access point name(APN), an identifier of a user-plane core network device, an address(for example, an IP address) of the user-plane core network device, andan IP address allocated by the user-plane core network device to userequipment.

The QoS flow-based QoS architecture mainly includes QoS flow mapping inan access stratum and a non-access stratum. The access stratum isresponsible for mapping a QoS flow to a DRB, and the non-access stratumis responsible for mapping an IP flow to a QoS flow. Further, mappinganother type of data packets to a QoS flow is further included. For aprocess of mapping a QoS flow to a DRB, refer to FIG. 3. In a protocolstack on a radio access network side linked to the NGC, a Service DataAdaption Protocol (SDAP) layer is used above a Packet Data ConvergenceProtocol (PDCP) layer on a user plane, and the SDAP protocol layer isresponsible for mapping a QoS flow from the non-access stratum to a DRBin the access stratum. An SDAP entity that executes the SDAP protocol isestablished based on a session, and is further responsible for adding anuplink QoS flow ID and a downlink QoS flow ID to an air-interfaceprotocol stack. In the process of mapping a QoS flow to a DRB, aplurality of QoS flows in a same session may be mapped to a same DRB.Same forwarding processing may be performed on data packets in a sameDRB based on a QoS profile (the QoS profile is a QoS parametercorresponding to a QoS flow ID, and includes one or more of a delay, apacket loss rate, a priority, a guaranteed rate, a maximum rate, and anunsatisfied rate notification indication) corresponding to a QoS flow IDin a header of a data packet on the user plane. QoS flows in differentsessions cannot be mapped to a same DRB. Further, each session of eachterminal corresponds to a default DRB. The terminal maps, to the defaultDRB, a QoS flow for which a mapping relationship between an uplink QoSflow and a DRB is not configured. Further, the gNB on the radio accessnetwork side may configure, for the terminal, the mapping relationshipbetween an uplink QoS flow and a DRB by using radio resource control(RRC) signaling or through reflective mapping (reflective mapping meansthat a downlink data packet includes a QoS flow ID, and the terminaldetects the QoS flow ID and maps uplink QoS flows with the same QoS flowID to a same DRB).

A reflective QoS characteristic may be used for mapping in a process ofmapping an IP flow or another type of data packets to a QoS flow. Thecore network may activate the reflective QoS characteristic by using acontrol plane or the user plane. Specifically, the core network maynotify, by using a non-access stratum message, the terminal that areflective QoS characteristic of a QoS flow is activated. For example,indication information indicating that the reflective QoS characteristicof the QoS flow is activated is included in a rule of the QoS flow, or areflective QoS indicator (RQI) is included in a header of a data packetto be sent from the core network to the radio access network side toindicate that the data packet has the reflective QoS characteristic. Forexample, in FIG. 4, a downlink data packet includes a QoS flow ID, an IPheader, a Transmission Control Protocol (TCP) header, and data content.In this case, an uplink QoS rule is to reverse sources and destinationsof the IP header and the TCP header. To be specific, an uplink sourceaddress is a downlink destination address, an uplink source port numberis a downlink destination port number, an uplink destination address isa downlink source address, and an uplink destination port number is adownlink source port number. The terminal obtains a packet filter of anuplink packet and a QoS flow ID of the uplink packet based on thereflective characteristic by using header information of the downlinkdata packet, and performs QoS marking by using the QoS flow ID. Theterminal implicitly configures mapping from an uplink QoS flow to a DRB.To be specific, the terminal maps an uplink QoS flow to a DRB in which adownlink QoS flow having a same QoS flow ID as the uplink QoS flow islocated. As shown in FIG. 5, an uplink flow 1 is mapped to a DRB 1 inwhich a downlink flow 1 is located. The radio access network side mayreduce RRC configuration signaling used for configuring mapping of anuplink flow to a radio bearer. However, for each received downlink datapacket, the terminal needs to determine whether the each receiveddownlink data packet has the reflective QoS characteristic. In a 5Gcommunications system, a data transmission rate is extremely high, andif the terminal detects each downlink data packet, extremely largeoverheads are caused, affecting performance and power consumption of theterminal.

In view of this, an embodiment of this application provides a reflectiveQoS characteristic-based communications method. In the method, anaccess-network network element determines whether there is a need tosend a QoS flow identifier to a terminal. The access-network networkelement sends a QoS flow identifier to the terminal when determiningthat there is a need to send the QoS flow identifier to the terminal, orthe access-network network element does not send a QoS flow identifierto the terminal when there is no need to send the QoS flow identifier tothe terminal, so as to save signaling overheads. Further, theaccess-network network element may filter a to-be-sent QoS flowidentifier. A QoS flow identifier is included in a header of a datapacket to be sent to the terminal, when determining that there is a needto add the QoS flow identifier to the header of the data packet; or aQoS flow identifier is not included in a header of a data packet to besent to the terminal, when there is no need to add the QoS flowidentifier to the header of the data packet, so as to save signalingoverheads.

FIG. 6 shows a reflective QoS characteristic-based communications methodaccording to an embodiment of this application. Referring to FIG. 6, themethod includes the following steps.

S101. A core-network network element sends first information to anaccess-network network element, and the access-network network elementreceives the first information sent by the core-network network element,where the first information is used to indicate whether a data packethas a reflective QoS characteristic.

In this application, the core-network network element may be a corenetwork control plane network element, such as an AMF. Theaccess-network network element may be a base station, such as a gNB.

When the core-network network element is a core network control planenetwork element, the core-network network element may send, to theaccess-network network element by using an N2 interface message, thefirst information used to indicate whether a data packet has thereflective QoS characteristic. The N2 interface message includes but isnot limited to a PDU session setup message (PDU Session Resource Setup),a PDU session modification message (PDU Session Resource Modify), or thelike.

The first information is used to indicate whether a data packet has thereflective QoS characteristic. If a data packet has the reflective QoScharacteristic, this means that the terminal can obtain an uplink QoSflow ID and an uplink packet filter based on the data packet in areflective manner. The packet filter is used to filter an uplink datapacket to obtain an uplink QoS flow. If a data packet does not have thereflective QoS characteristic, this means that the terminal cannotobtain an uplink QoS flow ID and an uplink packet filter based on thedata packet in a reflective manner.

S102. The access-network network element determines, based on the firstinformation, whether there is a need to send a QoS flow ID to aterminal.

S103. The access-network network element sends first indicationinformation to the terminal, where the first indication information isused to indicate whether the terminal needs to read a QoS flow ID.

The terminal receives the first indication information, and determines,based on the first indication information, whether there is a need toread a QoS flow ID.

In this embodiment of this application, if the first informationindicates that a data packet has the reflective QoS characteristic, theaccess-network network element determines that there is a need to send aQoS flow ID to the terminal. Optionally, in this case, theaccess-network network element notifies the terminal that there is aneed to read a QoS flow ID. Alternatively, if the first informationindicates that a data packet does not have the reflective QoScharacteristic, the access-network network element may determine thatthere is no need to send a QoS flow ID to the terminal. In this case,the access-network network element may notify the terminal that there isno need to read a QoS flow ID, so as to save signaling overheads.

In a possible implementation, the first information is further used toindicate a reflective QoS type of a data packet. The reflective QoS typeof a data packet includes: all data packets have the reflective QoScharacteristic, some data packets have the reflective QoScharacteristic, or none of data packets have the reflective QoScharacteristic.

The access-network network element may determine, based on the firstinformation, whether a data packet has the reflective QoScharacteristic, and determine, based on the reflective QoS type of adata packet, whether all data packets have the reflective QoScharacteristic, some data packets have the QoS reflective QoScharacteristic, or none of data packets have the reflective QoScharacteristic. The access-network network element may also determine,based on the reflective QoS type of a data packet, whether a data packethas the reflective QoS characteristic.

In this embodiment of this application, the reflective QoS type of adata packet may be indicated in the following manner. For example, thecore-network network element may notify, in a manner in which thecore-network network element notifies the terminal of the reflective QoScharacteristic by using a control plane message in a non-access stratum,the terminal that all data packets have the reflective QoScharacteristic; or notify, in a manner of adding an indication to auser-plane packet header, the terminal that some data packets have thereflective QoS characteristic. The core-network network elementnotifies, in a manner in which the core-network network element does notnotify the terminal of the reflective QoS characteristic or thecore-network network element notifies the terminal that a QoS flow or aPDU session does not have the reflective QoS characteristic, theterminal that none of data packets have the reflective QoScharacteristic.

In this embodiment of this application, the core-network network elementmay instruct the access-network network element to notify the terminalof the reflective QoS characteristic, so as to notify the terminalwhether a data packet has the reflective QoS characteristic and notifythe terminal of a reflective QoS type of the data packet.

With reference to actual application, the embodiments of thisapplication describe below an implementation process in which theaccess-network network element in this embodiment of this applicationdetermines whether there is a need to send a QoS flow ID to theterminal.

In a possible implementation of this application, the first informationmay be reflective QoS information sent by a core network control planenetwork element, and the reflective QoS information is used to indicatewhether a data packet has the reflective QoS characteristic. The firstindication information is reflective QoS information sent by theaccess-network network element to the terminal.

FIG. 7 is a flowchart of an implementation method of a reflective QoScharacteristic-based communications method according to an embodiment ofthis application. Referring to FIG. 7, the method includes the followingsteps.

S201. A core network control plane network element sends reflective QoSinformation to an access-network network element, where the reflectiveQoS information is used to indicate whether a data packet has areflective QoS characteristic.

Further, the reflective QoS information may be information used toindicate a reflective QoS type of a data packet.

In this embodiment of this application, the reflective QoS informationmay be reflective QoS information of a QoS flow, or may be reflectiveQoS information of a PDU session. In other words, the core networkcontrol plane network element may indicate reflective QoS information ofa QoS flow or reflective QoS information of a PDU session by using an N2interface message.

For the reflective QoS information, the reflective QoS information of aQoS flow or reflective QoS information of a PDU session may be indicatedby using a PDU Session Resource Setup message, or the reflective QoSinformation of a QoS flow or the reflective QoS information of a PDUsession may be indicated by using a PDU Session Resource Modify message.

A protocol format in which the reflective QoS information of a QoS flowis indicated by using the PDU Session Resource Setup message may beshown in Table 1. A protocol format in which the reflective QoSinformation of a PDU session is indicated by using the PDU SessionResource Setup message may be shown in Table 2.

TABLE 1 >>QoS Flows To Be Setup 1 List >>>QoS Flows To Be 1 . . .<maxnoof Setup Item IEs QoSFlows> >>>>QoS Flow Indicator M >>>>QoS FlowLevel QoS FFS Parameters >>>>Whether the QoS Enumerate {yes, no} flowhas the reflective QoS characteristic Reflective QoS Enumerate {all datacharacteristic packets have the reflective QoS characteristic, some datapackets have the reflective QoS characteristic}, if the QoS flow has thereflective QoS characteristic.

TABLE 2 >>PDU Session ID M (FFS) >>>>Whether the Enumerate {yes, no},and herein this is for all PDU session has the QoS flows in the PDUsession. reflective QoS characteristic Reflective QoS Enumerate {alldata packets have the reflective QoS characteristic characteristic, somedata packets have the reflective QoS characteristic}, if the PDU sessionhas the reflective QoS characteristic.

A protocol format in which the reflective QoS information of a QoS flowis indicated by using the PDU Session Resource Modify message may beshown in Table 3. A protocol format in which the reflective QoSinformation of a PDU session is indicated by using the PDU SessionResource Setup message may be shown in Table 4.

TABLE 3 >>QoS Flows To 0 . . . 1 Add Or Modify List >>>QoS Flows To 1 .. . <maxnoof Add Or Modify Item QoSFlows> IEs >>>>QoS Flow MIndicator >>>>QoS Flow O Level QoS Parameters >>>>Whether the Enumerate{yes, no} QoS flow has the reflective QoS characteristic Reflective QoSEnumerate {all data characteristic packets have the reflective QoScharacteristic, some data packets have the reflective QoScharacteristic}, if the QoS flow has the reflective QoS characteristic.

TABLE 4 >>PDU Session ID M (FFS) >>>>Whether the Enumerate {yes, no},and herein this is for all QoS PDU session has the flows in the PDUsession. reflective QoS characteristic Reflective QoS Enumerate {alldata packets have the reflective QoS characteristic characteristic, somedata packets have the reflective QoS characteristic}, if the PDU sessionhas the reflective QoS characteristic.

In a possible implementation of this embodiment of this application, thecore network control plane network element may further send reflectiveQoS information update indication information to the access-networknetwork element, and the reflective QoS information update indicationinformation is used to instruct the access-network network element toupdate the received reflective QoS information.

The core network control plane network element (such as an AMF) may sendthe reflective QoS information update indication information to theaccess-network network element (such as a base station) by using the N2interface message. The used N2 interface message includes but is notlimited to the PDU Session Resource Modify message.

In this application, the reflective QoS information that the reflectiveQoS information update indication information instructs theaccess-network network element to update is the same as the foregoingreflective QoS information. For details, refer to related descriptionsof the reflective QoS information in the foregoing embodiment. Detailsare not described herein again.

S202. The access-network network element receives the reflective QoSinformation sent by the core network control plane network element, anddetermines, based on the reflective QoS information sent by the corenetwork control plane network element, whether there is a need to send aQoS flow ID to a terminal.

When determining that a data packet has the reflective QoScharacteristic, the access-network network element determines that thereis a need to send a QoS flow ID to the terminal; or when determiningthat a data packet does not have the reflective QoS characteristic, theaccess-network network element determines that there is no need to senda QoS flow ID to the terminal, so as to save signaling overheads.

The access-network network element may determine, based on thereflective QoS information of a QoS flow or a PDU session, whether toadd a QoS flow ID to a header of a data packet to be sent through an airinterface. For example, for a data packet that has the reflective QoScharacteristic, a QoS flow ID is included in a header of the data packetto be sent through the air interface. For a data packet that does nothave the reflective QoS characteristic, a QoS flow ID is not included ina header of the data packet to be sent through the air interface, so asto save signaling overheads.

Further, the access-network network element may determine a mappingrelationship between a QoS flow and a DRB based on the reflective QoSinformation of a QoS flow or a PDU session, for example, theaccess-network network element may map QoS flows that vary in thereflective QoS characteristic to different DRBs.

In another possible implementation, the access-network network elementin this embodiment of this application may send the reflective QoSinformation to the terminal after receiving the reflective QoSinformation sent by the core network control plane network element, sothat the terminal determines whether a data packet has reflective QoSinformation, so as to determine whether there is a need to detect a QoSflow ID. For example, the method shown in FIG. 7 further includes thefollowing step:

S203. The access-network network element sends the reflective QoSinformation to the terminal.

In this embodiment of this application, the access-network networkelement (such as a base station) sends the reflective QoS information tothe terminal by using RRC signaling or a user plane control PDU.

In this embodiment of this application, the reflective QoS informationsent by the access-network network element to the terminal is similar tothe foregoing reflective QoS information sent by the core-networknetwork element to the terminal, and a difference lies in that thereflective QoS information sent by the access-network network element tothe terminal may be reflective QoS information of a QoS flow, reflectiveQoS information of a DRB, or reflective QoS information of a PDU session(or an SDAP entity). In other words, the access-network network elementmay notify the terminal of reflective QoS information of a QoS flow,reflective QoS information of a DRB, or reflective QoS information of aPDU session (or an SDAP entity).

A protocol format of the reflective QoS information of a QoS flow may beshown in FIG. 5.

TABLE 5 >QoS flow list 1 >>QoS flow ID {1 . . . maxnumber} >>>>Whetherthe Enumerate {yes, no} QoS flow has the reflective QoS characteristicReflective QoS Enumerate {all data packets have the reflective QoScharacteristic characteristic, some data packets have the reflective QoScharacteristic}, if the QoS flow has the reflective QoS characteristic.

A protocol format of the reflective QoS information of a DRB may beshown in FIG. 6.

TABLE 6 >DRB list 1 >>DRB ID {1 . . . maxnumber} >>>>Whether theEnumerate {yes, no} DRB has the reflective QoS characteristic ReflectiveQoS Enumerate {all data packets have the reflective QoS characteristiccharacteristic, some data packets have the reflective QoScharacteristic}, if the DRB has the reflective QoS characteristic.

A protocol format of the reflective QoS information of a PDU session oran SDAP entity may be shown in FIG. 7.

TABLE 7 >>PDU 1 Session/SDAP entity list >>PDU Session {1 . . .maxnumber} ID/SDAP entity id >>>>Whether the Enumerate {yes, no} PDUsession or the SDAP entity has the reflective QoS characteristicReflective QoS Enumerate {all data packets have the reflectivecharacteristic QoS characteristic, some data packets have the reflectiveQoS characteristic}, if the PDU session or the SDAP entity has thereflective QoS characteristic.

The terminal receives the reflective QoS information sent by theaccess-network network element, and determines, based on the reflectiveQoS information, whether there is a need to read a QoS flow ID.

Further, the access-network network element may indicate a reflectiveQoS characteristic of a data packet by sending, to the terminal,indication information indicating whether the terminal needs to read aQoS flow ID. For example, the access-network network element sends, tothe terminal, indication information indicating whether the terminalneeds to read a QoS flow ID from a DRB or SDAP, so as to indicate thereflective QoS characteristic of a data packet.

Further, the access-network network element may send reflective QoSinformation update indication information to the terminal by using RRCsignaling or a user plane control PDU. Reflective QoS information thatthe reflective QoS information update indication information sent by theaccess-network network element to the terminal instructs the terminal toupdate is the same as the reflective QoS information sent by theaccess-network network element to the terminal, and details are notdescribed herein.

After receiving the reflective QoS information sent by theaccess-network network element, the terminal determines, based on thereflective QoS information, a data packet having the reflective QoScharacteristic. The terminal detects a QoS flow ID and a data packetheader for a DRB, an SDAP entity, or a QoS flow that includes a datapacket having the reflective QoS characteristic, and generates an uplinkQoS flow ID and a corresponding packet filter based on the detected QoSflow ID. However, the terminal may not detect a QoS flow ID and a datapacket header for a DRB, an SDAP entity, or a QoS flow of a data packetthat does not have the reflective QoS characteristic, so as to savesignaling overheads of the terminal.

In another possible embodiment of this application, for a QoS flow whoseQoS parameter is standardized, the core-network network element does notnotify the access-network network element of the QoS parameter of theQoS flow by using the N2 interface message, but adds a QoS flow ID to aheader of a data packet to be sent through an N3 interface. The QoS flowID corresponds to a set of standardized QoS parameters. In thisscenario, the core-network network element may not send a reflective QoScharacteristic of the QoS flow to the access-network network element.The access-network network element may consider by default that the QoSflow has the reflective QoS characteristic, and that some data packetshave the reflective QoS characteristic. Alternatively, after theaccess-network network element obtains an RQI by parsing a header of adata packet to be sent through an N3 interface, the access-networknetwork element determines that the QoS flow has the reflective QoScharacteristic and that some data packets have the reflective QoScharacteristic. The RQI is used to indicate that a data packet has thereflective QoS characteristic.

In still another possible embodiment of this application, thecore-network network element may send reflective QoS informationdeactivation indication information to the access-network networkelement. The reflective QoS information deactivation indicationinformation is used to indicate reflective QoS deactivation information.The reflective QoS deactivation information means that a data packethaving the reflective QoS characteristic as indicated by the reflectiveQoS information does not have the reflective QoS characteristic anylonger.

FIG. 8 is a flowchart of another implementation method of a reflectiveQoS characteristic-based communications method according to anembodiment of this application. Referring to FIG. 8, the method includesthe following steps.

An execution step of S301 is the same as an execution step of S201, anddetails are not described herein again.

S302. The core-network network element sends reflective QoS informationdeactivation indication information to the access-network networkelement.

In this embodiment of this application, the reflective QoS informationdeactivation indication information is used to notify the access-networknetwork element device of reflective QoS deactivation information, andthe reflective QoS deactivation information means that a data packethaving the reflective QoS characteristic as indicated by the reflectiveQoS information does not have the reflective QoS characteristic anylonger. Specifically, the reflective QoS deactivation information may beused to deactivate the reflective QoS characteristic for all datapackets or deactivate the reflective QoS characteristic for some datapackets.

In this embodiment of this application, the reflective QoS deactivationinformation that the reflective QoS information deactivation indicationinformation indicates may be reflective QoS deactivation information ofa QoS flow, or may be reflective QoS deactivation information of a PDUsession. It may be understood that, the core-network network elementnotifies the access-network network element that a data packet of a QoSflow does not have the reflective QoS characteristic any longer, or datapackets of all QoS flows in a PDU session do not have the reflective QoScharacteristic any longer. It may also be understood that the reflectiveQoS information deactivation indication information may be used toindicate deactivation of the reflective QoS characteristic for a datapacket of a QoS flow or for a PDU session whose {all packets have thereflective QoS characteristic} or whose {some packets have thereflective QoS characteristic}.

The reflective QoS information deactivation indication information maybe used to indicate deactivation of the reflective QoS characteristicfor one or more QoS flows or PDU sessions. When the reflective QoSinformation deactivation indication information indicates deactivationof the reflective QoS characteristic for a QoS flow, an identifier ofthe QoS flow, such as a QoS flow ID, is added to the reflective QoSdeactivation information. When the reflective QoS informationdeactivation indication information indicates deactivation of thereflective QoS characteristic for a PDU session, an identifier of thePDU session, such as a PDU session ID, is added to the reflective QoSdeactivation information.

In a possible implementation of this application, a core network controlplane network element (such as an AMF) may send the reflective QoSdeactivation information to the access-network network element (such asa base station) by using an N2 interface message. The N2 interfacemessage includes but is not limited to a PDU Session Resource Modifymessage, and may further use another standalone message.

In another possible implementation of this application, a core networkuser plane network element (such as a UPF) may send the reflective QoSinformation deactivation indication information to the access-networknetwork element (such as a base station) by sending a data packetthrough an N3 interface.

The reflective QoS information deactivation indication information maybe added to a header of the data packet at the N3 interface, so as toindicate deactivation of the reflective QoS characteristic for the datapacket.

Further, the reflective QoS information deactivation indicationinformation carried in the header of the data packet at the N3 interfacemay be added based on a QoS flow, or may be added based on a PDUsession. A plurality of pieces of indication information may be set fora same QoS flow or a same PDU session to enhance robustness.

S303. The access-network network element receives the reflective QoSinformation deactivation indication information, and deactivates thereflective QoS characteristic for a data packet based on the reflectiveQoS information deactivation indication information.

In a possible implementation, an example in which the core-networknetwork element sends the reflective QoS information deactivationindication information to the access-network network element (such as abase station) by sending a data packet through the N3 interface is usedfor description. If a header of a data packet at the N3 interfacereceived by the access-network network element carries a QoS flow ID andthe reflective QoS information deactivation indication information, thereflective QoS characteristic is deactivated for the QoS flow. If aheader of a data packet at the N3 interface received by theaccess-network network element does not carry a QoS flow ID but carriesonly the reflective QoS information deactivation indication information,it indicates that the reflective QoS characteristic is deactivated forthe PDU session. If a header of a data packet at the N3 interfacereceived by the access-network network element carries a PDU session IDand the reflective QoS information deactivation indication information,it indicates that a PDU session corresponding to the PDU session ID isto be deactivated. In this case, the reflective QoS characteristic isdeactivated for the PDU session corresponding to the PDU session ID.

S304. The access-network network element determines that there is noneed to send a QoS flow ID for a data packet whose reflective QoScharacteristic has been deactivated.

For example, for a QoS flow whose reflective QoS characteristic has beendeactivated, the access-network network element no longer adds a QoSflow ID to a header of a data packet that is of the QoS flow and that isto be sent through an air interface.

In a possible implementation, after obtaining the reflective QoSinformation, the access-network network element in this embodiment ofthis application may further send the reflective QoS informationdeactivation indication information to a terminal. The step of sending,by the access-network network element, the reflective QoS informationdeactivation indication information to a terminal may be performed basedon the method shown in FIG. 7, or may be performed based on the methodshown in FIG. 8. An example in which the step is performed based on themethod shown in FIG. 8 is used for description below in this embodimentof this application. Based on the method in FIG. 8, the method mayfurther include the following step:

S305. The access-network network element sends the reflective QoSinformation deactivation indication information to a terminal.

In this embodiment of this application, reflective QoS deactivationinformation that the reflective QoS information deactivation indicationinformation sent by the access-network network element to the terminalindicates is similar to the foregoing reflective QoS deactivationinformation that the reflective QoS information deactivation indicationinformation sent by the core-network network element to theaccess-network network element indicates. A difference lies in that thereflective QoS deactivation information that the reflective QoSinformation deactivation indication information sent by theaccess-network network element to the terminal indicates may be not onlyreflective QoS deactivation information of a QoS flow or a PDU session,but also reflective QoS deactivation information of a DRB.

In this embodiment of this application, the access-network networkelement may deactivate reflective QoS information by using RRC signalingor a user plane control PDU, so as to indicate that a data packet doesnot have the reflective QoS characteristic any longer.

For example, the access-network network element may send the reflectiveQoS information deactivation indication information to the terminal byusing RRC signaling (such as an RRC configuration message or an RRCreconfiguration message) or a user plane control PDU (an SDAP controlPDU or a PDCP control PDU), and adds a QoS flow ID to the reflective QoSinformation deactivation indication information, so as to indicate thata data packet of a QoS flow does not have the reflective QoScharacteristic any longer.

For another example, the access-network network element may send thereflective QoS information deactivation indication information to theterminal by using RRC signaling (such as an RRC configuration message oran RRC reconfiguration message) or a user plane control PDU (an SDAPcontrol PDU or a PDCP control PDU), and adds a DRB ID to the reflectiveQoS information deactivation indication information, so as to indicatethat a data packet of a corresponding DRB does not have the reflectiveQoS characteristic any longer.

For still another example, the access-network network element may sendthe reflective QoS information deactivation indication information tothe terminal by using RRC signaling (such as an RRC configurationmessage or an RRC reconfiguration message) or a user plane control PDU(an SDAP control PDU or a PDCP control PDU), and adds a PDU session IDor an SDAP entity ID to the reflective QoS information deactivationindication information, so as to indicate that a data packet of a PDUsession does not have the reflective QoS characteristic any longer.

In another embodiment of this application, the access-network networkelement may send the reflective QoS information deactivation indicationinformation to the terminal by using user plane data. For example, theaccess-network network element adds the reflective QoS informationdeactivation indication information to a header of a data packet to besent through an air interface, so as to indicate deactivation of thereflective QoS characteristic. For example, 1 bit is used to representthe reflective QoS information deactivation indication information, anda bit setting manner is used to indicate deactivation of the reflectiveQoS characteristic. The reflective QoS information deactivationindication information carried in the header of the air-interface datapacket may be used to deactivate the reflective QoS characteristic for adata packet of a QoS flow, a DRB, or a PDU session whose {all packetshave the reflective QoS characteristic} or whose {some packets have thereflective QoS characteristic}.

Further, the access-network network element each time may indicatereflective QoS deactivation information of one QoS flow.

Further, a plurality of pieces of reflective QoS informationdeactivation indication information may be set for a same QoS flow toenhance robustness. Alternatively, the reflective QoS informationdeactivation indication information is continuously sent, and if a basestation obtains an acknowledgment indicating that the terminal hasreceived a data packet, sending of the reflective QoS informationdeactivation indication information is stopped.

In a possible implementation, the access-network network element adds aQoS flow ID and the reflective QoS information deactivation indicationinformation to a header of a data packet to be sent through an airinterface, so as to indicate that the reflective QoS characteristic hasbeen deactivated for a QoS flow. Alternatively, the access-networknetwork element adds only the reflective QoS information deactivationindication information to a header of a data packet to be sent throughan air interface, so as to indicate that the reflective QoScharacteristic has been deactivated for a PDU session, or adds onlyindication information to a header of a data packet to be sent throughan air interface, so as to indicate that a range of the reflective QoSinformation deactivation indication information is a PDU session. Forexample, a PDU session ID or an SDAP entity ID corresponding to a PDUsession is carried.

In another possible implementation, the access-network network elementmay use a manner of instructing the terminal not to read a QoS flow IDany longer, so as to indicate that the reflective QoS characteristic hasbeen deactivated for a data packet.

S306. The terminal receives the reflective QoS information deactivationindication information sent by the access-network network element, anddetermines that there is no need to read a QoS flow ID of the datapacket that does not have the reflective QoS characteristic any longer.

For example, for a DRB that does not have the reflective QoScharacteristic any longer or a DRB of an SDAP entity or a PDU sessionthat does not have the reflective QoS characteristic any longer, theterminal does not read a QoS flow ID from a received PDCP SDU. In otherwords, the terminal does not detect a QoS flow ID for each received datapacket, so as to save signaling overheads.

In this embodiment of this application, the following operations may beperformed for a data packet that does not have the reflective QoScharacteristic, so as to save signaling overheads.

For example, for a received PDCP SDU, the terminal no longer obtains anIP quintuple (or another byte in a protocol data packet header, such asa MAC source address and a MAC destination address) of the data packet,so as to save signaling overheads.

For another example, the terminal no longer reads and identifies an SDAPheader of each data packet, so as to save signaling overheads.

Further, a decompression operation performed at a PDCP layer at areceive end of the terminal for robust header compression (ROHC) may beused to directly decompress a PDCP service data unit (SDU) from which aPDCP header is removed, and there is no need to perform an operationcaused by an SDAP header such as an initial decompression locationoffset operation. To be specific, the following operations do not needto be performed, so as to save signaling overheads: Existence of theSDAP header is first detected, then decompression starts to be performedafter the SDAP header is removed from the PDCP SDU, the SDAP header isre-added to content obtained after decompression, and so on.

Further, if the SDAP header is placed at a tail of a data packet, whenROCH header compression is performed for a received PDCP SDU at a PDCPlayer at a transmit end, an initial header compression location offsetoperation is not performed. An initial header decompression locationoffset operation is also not performed when decompression is performedat the PDCP layer at the receive end, so as to save signaling overheads.

Further, if a PDCP layer entity at the receive end fails to performheader decompression, the data packet continues to be delivered to anSDAP layer. An SDAP layer entity may read the SDAP header from the tailor a head of the data packet to obtain a QoS flow ID, and may obtain amapping relationship between an uplink QoS flow and a DRB based on areflective mapping rule. Then the SDAP layer entity discards the datapacket.

Further, after the PDCP entity at the receive end fails to perform theheader decompression operation, if the PDCP SDU carries the SDAP headeror a QoS flow ID, the PDCP entity at the receive end delivers the PDCPSDU to the SDAP layer and indicates that the header decompression fails.In this case, the SDAP layer may read the SDAP header from the tail or ahead of the data packet to obtain the QoS flow ID, and may obtain amapping relationship between an uplink QoS flow and a DRB based on areflective mapping rule. Then the SDAP layer entity discards the datapacket.

Further, in another possible implementation, after the headerdecompression operation performed at the PDCP layer at the receive endfails, if the PDCP SDU carries the SDAP header or a QoS flow ID, thePDCP layer at the receive end sends a PDCP status report to the transmitend to indicate that the data packet fails to be sent. A PDCP layer atthe transmit end retransmits the data packet after receiving the PDCPstatus report. Alternatively, the PDCP layer at the receive end sends astatus report to the transmit end to indicate that the data packet failsto be sent, provided that decompression performed at the receive endfails. A PDCP layer at the transmit end retransmits the data packetafter receiving the sent status report. For a data packet carrying a QoSflow ID, the PDCP layer at the transmit end deletes the data packet onlyafter receiving a PDCP status report that is sent by the receive end andthat indicates that the data packet is successfully received. The PDCPstatus report includes a data packet successfully received at thereceive end and/or a data packet that fails to be received at thereceive end, and includes a PDCP layer sequence number of a data packet.This manner is applicable to a case in which the SDAP header is added toa head and a tail of an SDU at the SDAP layer, or the like.

In this embodiment of this application, the core-network network elementmay notify the access-network network element of reflective QoSinformation of a QoS flow or a PDU session, and may instruct theaccess-network network element to deactivate the reflective QoScharacteristic for a QoS flow or a PDU session. The access-networknetwork element may obtain the reflective QoS information, so as todetermine whether to send a QoS flow ID through an air interface.

Further, the access-network network element notifies the terminal ofreflective QoS information of a QoS flow, a DRB, or a PDU session, andmay deactivate the reflective QoS characteristic for a QoS flow, a DRB,or a PDU session. The terminal may determine, based on the reflectiveQoS information, whether there is a need to read a QoS flow ID throughan air interface and whether there is a need to perform an ROHC locationoffset operation. For a DRB that does not have the reflective QoScharacteristic, the terminal does not detect a QoS flow ID, and does notperform an ROHC decompression location offset operation, so as to reducedetection work performed by the terminal for an air-interface datapacket and reduce overheads, thereby improving processing efficiency andsaving power.

In another reflective QoS characteristic-based communications methodprovided in this application, a QoS flow ID to be sent through an airinterface may be filtered, so as to decrease a quantity of QoS flow IDsto be sent through the air interface, thereby saving signalingoverheads. An implementation process of filtering a QoS flow ID to besent though an air interface may be performed based on the foregoingembodiment, or may be independently performed. This is not limited inthis embodiment of this application.

FIG. 9 is a flowchart of still another implementation method of areflective QoS characteristic-based communications method according toan embodiment of this application. Referring to FIG. 9, the methodincludes the following steps:

S401. An access-network network element determines data packet headerinformation.

S402. The access-network network element determines, based on the datapacket header information, whether there is a need to add a QoS flow IDto a header of a data packet to be sent to a terminal.

In this embodiment of this application, it is determined whether thereis a need to add a QoS flow ID to the header of the data packet to besent to the terminal, so as to filter a QoS flow ID to be sent throughan air interface.

In a possible implementation, a core-network network element sendspacket filter composition information to the access-network networkelement, and the access-network network element determines, based on thecorresponding packet filter composition information in the header of thedata packet, whether there is a need to add a QoS flow ID to the headerof the data packet to be sent to the terminal.

Further, the access-network network element may determine, based on thecorresponding packet filter composition information in the header of thedata packet, whether there is a need to add, to the header of the datapacket to be sent to the terminal, indication information used toindicate that the data packet has a reflective QoS characteristic.

FIG. 10 is a flowchart of an implementation method for filtering a QoSflow ID according to an embodiment of this application. Referring toFIG. 10, the method includes the following step:

S501. A core-network network element sends reflective QoS information toan access-network network element.

Further, the core-network network element may send packet filtercomposition information to the access-network network element.

The core-network network element sends the reflective QoS information tothe access-network network element, so as to notify the access-networknetwork element of a reflective QoS characteristic of a QoS flow or aPDU session and notify the access-network network element whether acontrol plane or a user plane is used, so that the access-networknetwork element determines whether all data packets have the reflectiveQoS characteristic or some data packets have the reflective QoScharacteristic.

The packet filter composition information sent by the core-networknetwork element to the access-network network element may be packetfilter composition information corresponding to the reflective QoScharacteristic of a QoS flow or a PDU session, for example, the packetfilter composition information may be an IP quintuple (a source address,a destination address, a source port number, a destination port number,and a protocol number), or a Media Access Control (MAC) source addressand a MAC destination address.

In a possible implementation, the method may further include step S502:

S502. The core-network network element may further send the packetfilter composition information to a terminal. For example, thecore-network network element may notify the terminal of packet filtercomposition information corresponding to the reflective QoScharacteristic of a QoS flow or a PDU session. For example, the packetfilter composition information may be an IP quintuple (a source address,a destination address, a source port number, a destination port number,and a protocol number), or a MAC source address and a MAC destinationaddress.

S502 is an optional step.

S503. The access-network network element receives the reflective QoSinformation and packet filter composition information that are sent bythe core-network network element, and determines, based on a part thatis in the header of the data packet and corresponds to the packet filtercomposition information, whether there is a need to add a QoS flow ID tothe header of the data packet to be sent to the terminal. Further, theaccess-network network element may determine whether there is a need toadd indication information to the header of the data packet to be sentto the terminal, and the indication information is used to indicate thatthe data packet has the reflective QoS characteristic.

In a scenario in which all data packets of a QoS flow have thereflective QoS characteristic:

The access-network network element performs packet detection for eachdata packet, of the QoS flow, that is received from an N3 interface, anddetects a header of the data packet based on packet filter composition.For example, if the packet filter composition is an IP quintuple, theaccess-network network element detects content of the IP quintuple inthe header of the data packet. If a part that is in the header of thedata packet and corresponds to a packet filter part is new content, forexample, the content of the IP quintuple in the header of the datapacket is new, it indicates that the access-network network element doesnot send, through an air interface, a data packet that carries a QoSflow ID and that has the same IP quintuple content. In this case, a QoSflow ID is carried when the data packet is to be sent through the airinterface, and indication information may be further carried to indicatethat the data packet has the reflective QoS characteristic.Alternatively, if a part that is in the header of the data packet andcorresponds to a packet filter is not new, a QoS flow ID is not carriedwhen the data packet is to be sent through the air interface, andindication information used to indicate that the data packet has thereflective QoS characteristic is not carried.

Further, if the access-network network element has acknowledged that theterminal has received a downlink data packet (and the data packetcarries a QoS flow ID) whose header includes the same content (the partcorresponding to the packet filter), or the access-network networkelement has successfully sent N downlink data packets that have the sameIP quintuple content (N may be set by a network, for example, set by thecore-network network element or the access-network network element), theaccess-network network element does not add a QoS flow ID to the datapacket when sending the data packet through the air interface, and doesnot add, to the data packet, the indication information indicating thatthe data packet has the reflective QoS characteristic.

In a scenario in which some data packets of a QoS flow have thereflective QoS characteristic:

The access-network network element performs packet detection for a datapacket that is received from an N3 interface and that carries the QoSflow ID and an RQI, and detects a header of the data packet based onpacket filter composition information. For example, if packet filtercomposition is an IP quintuple, the access-network network elementdetects content of the IP quintuple in the header of the data packet. Ifa part that is in the header of the data packet and corresponds to apacket filter part is new, for example, the content of the IP quintuplein the header of the data packet is new content, it indicates that theaccess-network network element does not send, through an air interface,a data packet that carries a QoS flow ID and that has the same IPquintuple content. In this case, a QoS flow ID is carried when the datapacket is to be sent through the air interface, and indicationinformation may be further carried to indicate that the data packet hasthe reflective QoS characteristic. If a part that is in the header ofthe data packet and corresponds to the packet filter composition is notnew, a QoS flow ID is not carried when the data packet is to be sentthrough the air interface.

Further, if the access-network network element has acknowledged that theterminal has received a downlink data packet (and the data packetcarries a QoS flow ID) whose header includes the same content (the partcorresponding to the packet filter), or the access-network networkelement has successfully sent the N downlink data packets (N may be setby a network, for example, set by the core-network network element orthe access-network network element), the access-network network elementdoes not add a QoS flow ID to the data packet when sending the datapacket through the air interface, and does not add, to the data packet,the indication information indicating that the data packet has thereflective QoS characteristic.

In this embodiment of this application, a QoS flow ID to be sent throughthe air interface is filtered in this manner, so that a quantity ofto-be-sent QoS flow IDs is decreased, and operations of detecting a QoSflow ID and obtaining a packet filter by the terminal can be reduced,thereby reducing overheads of the terminal.

In another possible implementation, if the access-network networkelement determines that there is a need to add a QoS flow ID to theheader of the data packet to be sent to the terminal, the access-networknetwork element sends a user plane control PDU or radio resource controlRRC signaling to the terminal. The user plane control PDU and the RRCsignaling both include a QoS flow ID of the data packet and headerinformation of the data packet.

FIG. 11 is a flowchart of another implementation method for filtering aQoS flow ID according to an embodiment of this application. Referring toFIG. 11, the method includes the following steps.

Execution steps of S601, S602, and S603 are the same as execution stepsof S501, S502, and S503. Details are not described herein again, andonly a difference is described below.

S604. If the access-network network element determines that there is aneed to add a QoS flow ID to the header of the data packet to be sent tothe terminal, the access-network network element sends a user planecontrol PDU (such as an SDAP control PDU or a PDCP control PDU) or RRCsignaling (including but not limited an RRC configuration message, anRRC reconfiguration message, or the like) to the terminal, where theuser plane control PDU and the RRC signaling both include a QoS flow IDof the data packet and header information of the data packet.

In a scenario in which all data packets of a QoS flow have thereflective QoS characteristic:

The access-network network element performs packet detection for a datapacket that is received from an N3 interface and that carries the QoSflow ID and an RQI, and detects a header of the data packet based onpacket filter composition information. For example, if packet filtercomposition is an IP quintuple, the access-network network elementdetects content of the IP quintuple in the header of the data packet. Ifa part that is in the header of the data packet and corresponds to apacket filter part is new content, for example, the content of the IPquintuple in the header of the data packet is new content, it indicatesthat the access-network network element does not send, through an airinterface, a data packet that carries a QoS flow ID and that has thesame IP quintuple content. In this case, a user plane control PDU/RRCsignaling is generated to notify the terminal. The user plane controlPDU or the RRC signaling includes the QoS flow ID of the data packet andthe header of the data packet, or includes the QoS flow ID of the datapacket and partial content (corresponding to the packet filtercomposition, for example, a source IP address is x, a destination IPaddress is y, a source port number is 22, a destination port number is67, and a protocol number is TCP) of the header of the data packet.

If a part that is in the header of the data packet and corresponds to apacket filter part is not new, the user plane control PDU and the RRCsignaling are not generated.

Further, if the access-network network element has acknowledged that theterminal has received a user plane control PDU or RRC signaling thatincludes the same content, the access-network network element no longersends a user plane control PDU. The access-network network element doesnot add a QoS flow ID to the data packet when sending the data packetthrough the air interface.

In a scenario in which some packets of a QoS flow have the reflectiveQoS characteristic, the access-network network element performs packetdetection for only a data packet, of the QoS flow, that is received froman N3 interface and that carries an RQI, and other operations are thesame as those specific to the scenario in which all packets of a QoSflow have the reflective QoS characteristic.

In still another possible implementation, if the access-network networkelement determines that there is a need to add a QoS flow ID to theheader of the data packet to be sent to the terminal, the access-networknetwork element performs, based on the packet filter compositioninformation, a reflective operation on content that is in the header ofthe data packet and corresponds to the packet filter compositioninformation, so as to obtain an uplink packet filter. The access-networknetwork element sends the uplink packet filter and the QoS flow ID tothe terminal.

FIG. 12 is a flowchart of still another implementation method forfiltering a QoS flow ID according to an embodiment of this application.Referring to FIG. 12, the method includes the following steps.

Execution steps of S701, S702, and S703 are the same as execution stepsof S501, S502, and S503. Details are not described herein again, andonly a difference is described below.

S704. If the access-network network element determines that there is aneed to add a QoS flow ID to the header of the data packet to be sent tothe terminal, the access-network network element performs, based on thepacket filter composition information, a reflective operation on contentthat is in the header of the data packet and corresponds to the packetfilter composition information, so as to obtain an uplink packet filter.

The access-network network element may perform a reflective operation oncontent that is in a header of a downlink data packet and corresponds toa packet filter, so as to obtain an uplink packet filter. For example,the access-network network element reverses IP quintuple content in theheader of the downlink data packet, that is, interchanges a sourceaddress and a destination address, and interchanges a source port numberand a destination port number, so as to obtain the uplink packet filter.For example, a filter may include the following content: a source IPaddress is y, a destination IP address is x, a source port number is 67,a destination port number is 22, and a protocol number is TCP.

S705. The access-network network element sends the uplink packet filterand the QoS flow ID to the terminal.

The access-network network element may send the uplink packet filter andthe QoS flow ID to the terminal. The access-network network element maynotify the terminal of the uplink packet filter and the QoS flow ID byusing a user plane control PDU or RRC signaling.

In a possible embodiment, the access-network network element may furthernotify the terminal that the sent packet filter is an uplink packetfilter. The terminal receives the QoS flow ID and the correspondinguplink packet filter, so as to generate an uplink QoS flow.

In this embodiment of this application, the terminal is notified of theuplink QoS flow ID and the corresponding uplink packet filter by usingthe user plane control PDU or the RRC signaling, so that theaccess-network network element may not need to send the QoS flow ID byusing an air interface, and the terminal does not need to performoperations of detecting the QoS flow ID and obtaining the packet filter,thereby reducing overheads of the terminal to some extent.

Further, in this embodiment of this application, based on the methodshown in FIG. 10 to FIG. 12, the terminal may send, to theaccess-network network element, indication information used to indicatewhether the terminal has one or more of a capability of reading a QoSflow ID and a capability of generating an uplink packet filter.Alternatively, the terminal sends, to the access-network networkelement, indication information used to indicate whether a status of theterminal supports one or more of a capability of reading a QoS flow IDand a capability of generating an uplink packet filter.

FIG. 13 is a flowchart of still another implementation for filtering aQoS flow ID by an access-network network element according to anembodiment of this application. Referring to FIG. 13, the methodincludes the following steps.

Execution steps of S801, S802, and S803 in FIG. 13 are the same asexecution steps of S501, S502, and S503. Details are not describedherein again, and only a difference is described below.

S804. The terminal sends first capability information, and theaccess-network network element receives the first capability informationsent by the terminal.

The first capability information is used to indicate whether theterminal has at least one of a capability of reading a QoS flow ID and acapability of generating an uplink packet filter.

The capability of reading a QoS flow ID is a capability of obtaining, bythe terminal, a QoS flow ID from a received air-interface data packet.The capability of generating an uplink packet filter is a capability ofgenerating, by the terminal, an uplink packet filter based on a receiveddownlink air-interface data packet.

The terminal may report the first capability information to theaccess-network network element by using RRC signaling; or the terminalmay report the first capability information to the core-network networkelement, and the core-network network element notifies theaccess-network network element of the first capability information.

An execution sequence of S801, S802, S803, and S504 is not limited inthis embodiment of this application. For example, an execution step ofS504 may be before S801, S802, and S803.

Further, the terminal may report a reflective mapping capability. Thereflective mapping capability is a capability of obtaining, by theterminal, a mapping relationship between an uplink QoS flow and a DRBbased on a QoS flow ID carried in a header of a downlink data packet.For ease of description, the reflective mapping capability reported bythe terminal may be referred to as second capability information. Theterminal may further send the second capability information, and theaccess-network network element receives the second capabilityinformation sent by the terminal.

The terminal may report the reflective mapping capability information tothe access-network network element by using RRC signaling; or theterminal may report the reflective mapping capability information to thecore-network network element, and the core-network network elementnotifies the access-network network element of the reflective mappingcapability information.

If the access-network network element determines that the terminal doesnot support the reflective mapping capability, the access-networknetwork element needs to configure, for the terminal in another manner,the mapping relationship between an uplink QoS flow and a DRB, forexample, configure the mapping relationship between an uplink QoS flowand a DRB by using RRC signaling. The RRC signaling may include but isnot limited to an RRC configuration message, an RRC reconfigurationmessage, or the like.

Further, the access-network network element may determine, based onwhether the terminal has the capability of reading a QoS flow ID,whether the terminal supports the reflective mapping capability. If theterminal supports the capability of reading a QoS flow ID, the terminalhas the reflective mapping capability; or if the terminal does notsupport the capability of reading a QoS flow ID, the terminal does nothave the reflective mapping capability.

S805. If the access-network network element determines that a capabilityor a status of the terminal does not support the capability of reading aQoS flow ID and a capability of generating an uplink packet filter, theaccess-network network element notifies, by using a user plane controlPDU or RRC signaling, the terminal of a QoS flow ID and an uplink packetfilter corresponding to the QoS flow ID.

S806. If the access-network network element determines that the terminalsupports the capability of generating an uplink packet filter, theaccess-network network element may send the QoS flow ID and a datapacket header part to the terminal by using an air-interface datapacket.

In this embodiment of this application, the access-network networkelement may notify, by using the user plane control PDU or the RRCsignaling, the terminal of the QoS flow ID and the uplink packet filtercorresponding to the QoS flow ID, so as to reduce overheads of theterminal and reduce overheads caused if the QoS flow ID is carriedthrough an air interface.

In another reflective QoS characteristic-based communications methodprovided in this application, the access-network network element mayfilter the to-be-sent first information used to indicate whether a datapacket has the reflective QoS characteristic, so as to save signalingoverheads. An implementation process of filtering the first informationmay be performed based on the foregoing embodiment, or may beindependently performed. This is not limited in this embodiment of thisapplication.

FIG. 14 is a flowchart of implementation of another reflective QoScharacteristic-based communications method according to an embodiment ofthis application. Referring to FIG. 14, the method includes thefollowing steps.

S901. A core-network network element sends a QoS rule validity time toan access-network network element.

In this embodiment of this application, the QoS rule validity time isused to indicate activation and deactivation of a QoS rule, and the QoSrule is effective in the QoS rule validity time. The QoS rule is a QoSrule obtained by using a reflective QoS characteristic.

The QoS rule validity time sent by the core-network network element tothe access-network network element may be a QoS rule validity time of aQoS flow, or may be a QoS rule validity time of a PDU session.

Specifically, the core-network network element may send a QoS rulevalidity time of one or more QoS flows to the access-network networkelement at one time. If the QoS rule validity time sent by thecore-network network element to the access-network network element is aQoS rule validity time of a PDU session, the QoS rule validity time ofthe PDU session is applicable to all QoS flows in the corresponding PDUsession that have the reflective QoS characteristic.

The core-network network element may send the QoS rule validity time tothe access-network network element by using an N2 interface message. TheN2 interface message includes but is not limited to a PDU session setupmessage (PDU Session Resource Setup), a PDU session modification message(PDU Session Resource Modify), or the like.

S902. The access-network network element receives the QoS rule validitytime sent by the core-network network element, and if the access-networknetwork element receives, in the QoS rule validity time, at least twodata packets having the reflective QoS characteristic, theaccess-network network element may send, for some of the at least twodata packets in the QoS rule validity time, first information used toindicate whether a data packet has the reflective QoS characteristic.

In this embodiment of this application, if the access-network networkelement receives a plurality of data packets having the reflective QoScharacteristic, and determines that receiving time of the plurality ofdata packets having the reflective QoS characteristic is in the QoS rulevalidity time, the access-network network element may send, for onlysome of the plurality of received data packets, first information usedto indicate whether a data packet has the reflective QoS characteristic,and does not need to send the first information for all the datapackets, so as to filter the to-be-sent first information and savesignaling overheads.

The QoS rule validity time may be implemented by using a timer. Forexample, if the access-network network element determines that a datapacket has the reflective QoS characteristic, the access-network networkelement generates a QoS rule (including at least one of a QoS rule ID, aQoS flow ID, a packet filter, a priority, or the like) based on thisdata packet, and starts a timer. If a QoS rule having the same packetfilter exists in the access-network network element, the access-networknetwork element may restart the timer. If the timer expires, thecorresponding QoS rule is deleted. Before the timer expires, if theaccess-network network element receives N data packets having thereflective QoS characteristic from a core network user plane networkelement, the access-network network element may send the firstinformation for M data packets, where M is less than N, and both M and Nare positive integers. In this embodiment of this application, the firstinformation used to indicate whether a data packet has the reflectiveQoS characteristic may include one or more of a QoS flow ID and anon-access stratum reflective QoS indicator (NAS reflective QoSindicator, NRQI).

In this embodiment of this application, for a QoS flow whose reflectiveQoS is controlled by using a control plane, each data packet received bythe access-network network element from the core network user planenetwork element has the reflective QoS characteristic. Therefore, theaccess-network network element may filter the first information to besent for all the received data packets of the QoS flow. However, for aQoS flow whose QoS is controlled by using a user plane, only a datapacket that carries an RQI and that is received by the access-networknetwork element from the core network user plane network element has thereflective QoS characteristic. Therefore, the access-network networkelement may filter the first information to be sent for a received datapacket having the reflective QoS characteristic.

S903. The access-network network element may send the QoS rule validitytime to a terminal after receiving the QoS rule validity time, so thatthe terminal maps, in the QoS rule validity time by using a same QoSrule, data packets having the reflective QoS characteristic into a QoSflow.

The QoS rule validity time may be implemented by using a timer. Forexample, if the terminal determines that a data packet has thereflective QoS characteristic, the terminal generates a QoS rule(including at least one of a QoS rule ID, a QoS flow ID, a packetfilter, a priority, or the like) based on this data packet, and starts atimer. If a QoS rule having the same packet filter exists in theterminal, the terminal may restart the timer. If the timer expires, thecorresponding QoS rule is deleted.

In still another possible design, the core-network network element mayfurther send QoS rule validity time update information to theaccess-network network element, and the QoS rule validity time updateinformation is used to indicate an updated QoS rule validity time. TheQoS rule validity time update information may be QoS rule validity timeupdate information of a QoS flow, or may be QoS rule validity timeupdate information of a PDU session.

In a cell handover process of the terminal or in a multi-connectionprocess, when a service of the terminal is switched, some or all QoSflows, of the terminal, in a source access-network network element (asource base station) may be switched to a target access-network networkelement (a target base station). The source access-network networkelement (the source base station) may send a QoS rule validity time of ato-be-switched QoS flow to the target access-network network element(the target base station) to which the terminal is to be handed over.The target access-network network element may filter, based on the QoSrule validity time, the reflective QoS information to be sent to theterminal, so as to filter the reflective QoS information to be sent tothe terminal, thereby saving signaling overheads.

The source access-network network element (the source base station) maysend the QoS rule validity time of the to-be-switched QoS flow to thetarget access-network network element (the target base station) by usinga message that includes but is not limited to a handover requestmessage, a secondary base station addition request message, a secondarybase station modification request message, or the like.

The QoS rule validity time that may be sent by the source access-networknetwork element to the target access-network network element to whichthe terminal is to be handed over may be a QoS rule validity time of aQoS flow, or may be a QoS rule validity time of a PDU session.

Further, when sending, in a target cell, a data packet of a QoS flow,the target access-network network element may ignore a QoS rule validitytime of a data packet sent by the source access-network network element,and filter the to-be-sent first information based on only a QoS rulevalidity time corresponding to the data packet sent from the targetaccess-network network element, so as to avoid QoS rule validity timesynchronization between the source access-network network element andthe target access-network network element.

In still another embodiment of this application, an SDAP frame format ina process in which an SDAP entity transmits a data packet may beoptimized so as to send a data packet of the foregoing QoS flow throughan air interface, where the SDAP entity is responsible for adding anuplink QoS flow ID and a downlink QoS flow ID to an air-interfaceprotocol stack.

In this embodiment of this application, a transparent-mode SDAP frameformat and a non-transparent-mode SDAP frame format may be configured.The transparent-mode SDAP frame format means that no SDAP header isconfigured for a DRB. In other words, an SDAP PDU does not include SDAPheader. The non-transparent-mode SDAP frame format means that an SDAPheader is configured for a DRB. In other words, an SDAP PDU includes theSDAP header.

In the embodiments of this application, the transparent-mode SDAP frameformat and the non-transparent-mode SDAP frame format are separatelydescribed below. The non-transparent-mode SDAP frame format is firstdescribed.

FIG. 15 is a schematic diagram of a downlink SDAP frame format accordingto an embodiment of this application. Referring to FIG. 15, an SDAPheader of the downlink SDAP frame format includes a non-access stratumQoS indicator (NAS reflective QoS indicator, NRQI) field and an accessstratum reflective mapping indicator (ARQI) field. The NRQI and the ARQIeach may be indicated by using a bit. If a bit used to indicate the NRQIis set to 1, it indicates that the data packet has a reflective QoScharacteristic. If a bit used to indicate the NRQI is set to 0, itindicates that the data packet does not have the reflective QoScharacteristic. If a bit used to indicate the ARQI is set to 1, itindicates that the QoS flow has a reflective mapping characteristic. Ifa bit used to indicate the ARQI is set to 0, it indicates that the QoSflow does not have the reflective mapping characteristic.

In FIG. 15, QFI represents a QoS flow identifier, Data represents data,R represents an idle bit, Qct represents a byte, and one byte occupieseight bits.

In a data packet transmission process, when an SDAP entity at a datatransmit end sends a data packet, if the SDAP entity determines that theto-be-sent data packet has the reflective QoS characteristic, the SDAPentity sets the bit used to indicate the NRQI to 1; or if the SDAPentity determines that the to-be-sent data packet does not have thereflective QoS characteristic, the SDAP entity sets the bit used toindicate the NRQI to 0. When the SDAP entity at the data transmit endsends a data packet, if the SDAP entity determines that a QoS flow ofthe to-be-sent data packet has the reflective mapping characteristic,the SDAP entity sets the bit used to indicate the ARQI to 1; or if theSDAP entity determines that a QoS flow of the to-be-sent data packetdoes not have the reflective mapping characteristic, the SDAP entitysets the bit used to indicate the ARQI to 0.

In a possible embodiment of this application, if the bit used toindicate the NRQI and the bit used to indicate the ARQI both are set to0, an SDAP header may not carry a QoS flow identifier (QoS flow ID, QFI)field. If at least one of the bit used to indicate the NRQI and the bitused to indicate the ARQI is set to 1, the QFI field is carried.

The SDAP entity at the data transmit end generates the SDAP header inthe foregoing manner, and delivers the SDAP header and a data packetreceived from a UPF to a PDCP layer.

In a data packet transmission process, an SDAP entity at a data receiveend receives a PDCP SDU from the PDCP layer, and reads the SDAP header.If a value of the bit used to indicate the NRQI is 1, it indicates thatthe data packet has the reflective QoS characteristic. In this case, theSDAP entity delivers, to an upper layer such as a NAS layer, a dataportion of SDAP and a QoS flow ID that is read from the SDAP header. Thedata portion and the QoS flow ID that are delivered to the upper layermay be used to generate a QoS rule at the upper layer. Further, the SDAPentity may send the NRQI to the upper layer. If the value of the bitused to indicate the NRQI is 0, it indicates that the data packet doesnot have the reflective QoS characteristic. The SDAP entity sends onlythe data portion of SDAP to the upper layer such as the NAS layer. If avalue of the bit used to indicate the ARQI is 1, it indicates that theQoS flow has the reflective mapping characteristic, and the SDAP entitygenerates, based on a downlink QoS flow ID read from the data packet anda DRB ID corresponding to the data packet, a mapping relationshipbetween an uplink QoS flow and a DRB. If the value of the bit used toindicate the ARQI is 0, it indicates that the QoS flow does not have thereflective mapping characteristic. The SDAP entity does not generate themapping relationship between an uplink QoS flow and a DRB based on thedownlink QoS flow ID. If the bit used to indicate the NRQI and the bitused to indicate the ARQI both are set to 0, the SDAP entity may learnthat a subsequent part of the SDAP frame format does not carry the QFIfield, and may learn a start location of the data packet. For example,as shown in FIG. 16, the SDAP entity may learn that the data portionstarts from a second byte.

FIG. 17 is a schematic diagram of a downlink SDAP frame format accordingto an embodiment of this application. The SDAP frame format shown inFIG. 17 is similar to the SDAP frame format shown in FIG. 15, and adifference lies in that an SDAP header further includes a bit used toindicate user plane reflective QoS flow indication information (UPreflective QoS indicator, URQI). The URQI is used to indicate whetherreflective QoS is controlled by using a user plane. In other words, theURQI is used to indicate whether the reflective QoS is indicated by aUPF by adding an RQI to a data packet to be sent through an N3interface. If the reflective QoS is indicated by the UPF by adding theRQI to the data packet to be sent through the N3 interface, a value ofthe bit used to indicate the URQI is set to 1; or if the reflective QoSis not indicated by the UPF by adding the RQI to the data packet to besent through the N3 interface, a value of the bit used to indicate theURQI is set to 0.

In a data packet transmission process, when an SDAP entity at a datatransmit end sends a data packet, if the SDAP entity determines that adata packet received from the UPF carries the RQI, the value of the bitused to indicate the URQI is set to 1; or if the SDAP entity determinesthat a data packet received from the UPF does not carry the RQI, thevalue of the bit used to indicate the URQI is set to 0. An SDAP entityat a data receive end receives a PDCP SDU from a PDCP layer, and SDAPreads the SDAP header. If a value of a bit used to indicate an NRQI is1, it indicates that the data packet has a reflective QoScharacteristic, and the SDAP entity delivers a data portion of SDAP anda QoS flow ID that is read from the corresponding SDAP header to anupper layer such as a NAS layer. If a value of a bit used to indicate aURQI is 1, the SDAP entity further delivers, to the upper layer, an NRQIcorresponding to the data packet.

In the foregoing embodiment of this application, a data packet whoseSDAP header carries reflective QoS information of the NAS layer andreflective mapping information of an AS layer may be transferred throughan air interface, air-interface overheads may be reduced, and it may beaccurately determined whether to deliver RQI indication information tothe upper-layer protocol.

In a possible design, in this embodiment of this application, a bit maybe further set in the SDAP header, where the bit is used to indicatewhether transmission, in a corresponding DRB, of a data packet of a QoSflow ends. For example, an End field is set, and the End field is usedto indicate whether transmission, in a corresponding DRB, of a datapacket of a QoS flow ends.

FIG. 18 is a schematic diagram of another SDAP frame format according toan embodiment of this application. If a bit used to indicate an Endfield is set to 1, it indicates that transmission, in a correspondingDRB, of a data packet of the QoS flow ends. If the bit used to indicatean End field is set to 0, it indicates that transmission, in acorresponding DRB, of a data packet of the QoS flow does not end.

In a data packet transmission process, when an SDAP entity at a datatransmit end sends a data packet, if the SDAP entity determines to stopsending, in a DRB (such as a DRB 1), a data packet of a QoS flow (suchas a QoS flow 1), the SDAP entity sets a bit that is in an SDAP headerand that is used to indicate the End field to 1. Alternatively, an SDAPPDU is sent, and the SDAP PDU does not include a data field. In otherwords, the SDAP PDU is only used to indicate that data transmission, inthe DRB, of the data packet of the QoS flow ends. An SDAP entity at adata receive end receives a PDCP SDU from a PDCP layer, and SDAP readsthe SDAP header. If the bit used to indicate the End field is set to 1,it indicates that transmission, in the DRB, of the data packet of theQoS flow ends; or if the bit used to indicate the End field is set to 0,it indicates that transmission, in the DRB, of the data packet of theQoS flow does not end.

In this embodiment of this application, if the SDAP entity at the datareceive end determines that the bit used to indicate the End field isset to 1, the SDAP entity may feed back a receiving status of the datapacket of the QoS flow based on this information, for example, may feedback completion of receiving, in the DRB, of the data packet of the QoSflow.

Further, if the SDAP entity at the data receive end determines that thebit used to indicate the End field is set to 1, the SDAP entity at thedata receive end may further sort, based on this information, datapackets of a same QoS flow that are received from different DRBs.

It may be understood that this embodiment of this application may bebased on the SDAP frame format described in FIG. 15 to FIG. 17, and theEnd field is set in the SDAP frame format in the foregoing embodiment ofthis application. An SDAP frame format in which the End field is set maybe applied to protocol header design for an uplink SDAP frame format anda downlink SDAP frame format.

In still another possible design, in this embodiment of thisapplication, a control command may be further set in the SDAP header,where the control command is used to feed back completion of receiving,in a DRB, of a data packet of a QoS flow. FIG. 19 is a schematic diagramof still another SDAP frame format according to an embodiment of thisapplication. In FIG. 19, a D/C field indicates whether the PDU is acontrol PDU or a data PDU. For example, if a value of a bit used toindicate the D/C field is set to 1, it indicates that the PDU is acontrol PDU; or if a value of a bit used to indicate the D/C field isset to 0, it indicates that the PDU is a data PDU. A PDU type fieldindicates a type of a control PDU. For example, a value of the PDU typefield is 000, indicating a feedback about completion of receiving, in aDRB, of a data packet of a QoS flow.

In a data packet transmission process, when an SDAP entity at a datatransmit end sends a data packet, if the SDAP entity determines thatthere is a need to send a control PDU, the SDAP entity sets the D/Cfield to 1, and sets the PDU type field to a value corresponding to acontrol command, for example, sets the control command used to feed backcompletion of receiving, in a DRB, of a data packet of a QoS flow to000. An SDAP entity at a data receive end receives a PDCP SDU from aPDCP layer, and SDAP reads the SDAP header. If the D/C field is 1, itindicates that the SDAP PDU is a control PDU; or if the D/C field is not1, it indicates that the SDAP PDU is a data PDU. For a control PDU, theSDAP entity at the data receive end reads the PDU type field to obtain acorresponding control command. For example, the value of the PDU typefield is 000, indicating a control command used to feed back completionof receiving, in a DRB, of a data packet of a QoS flow.

It may be understood that in FIG. 15 to FIG. 19 in the embodiments ofthis application, an example in which a length of the QFI is 8 bits isused for description, but the length of the QFI is unnecessarily 8 bits.The embodiments of this application may further include a scenario inwhich the QFI has another different length.

Further, the QFI in the foregoing embodiment may be a QoS flow ID thatis in a NAS layer and that is generated by a terminal or a core networkuser plane network element, or may be a QoS flow ID that is in an ASlayer and that is configured by an access-network network element. Thereis a mapping relationship between the QoS flow ID in the NAS layer andthe QoS flow ID in the AS layer. For example, the QoS flow ID in the NASlayer and the QoS flow ID in the AS layer are in a one-to-onecorrespondence in a PDU session or a DRB.

The transparent-mode SDAP frame format is described below in theembodiments of this application.

In an embodiment of this application, a transparent-mode SDAP frameformat is configured. To be specific, no SDAP header is configured for aDRB, and an SDAP PDU does not include SDAP header. In other words, theSDAP PDU is an SDAP SDU. In this way, overheads caused if the SDAPheader is carried through an air interface are reduced, and there is noeffect on PDCP ROHC processing.

SDAP is configured based on a DRB. If transparent-mode SDAP isconfigured in a bidirectional manner, that is, transparent-mode SDAPneeds to be configured in both an uplink and a downlink, a mappingrelationship between a QoS flow and a DRB is restricted. In acorresponding downlink direction, only a QoS flow whose reflective QoSand reflective mapping are not activated can be mapped to a DRB forwhich transparent-mode SDAP is configured. In an uplink direction, onlya QoS flow that does not carry a QoS flow ID can be mapped to a DRB forwhich transparent-mode SDAP is configured.

If transparent-mode SDAP is configured based on the mapping relationshipbetween a QoS flow and a DRB, in a scenario in which a QoS flow ID needsto be carried in the uplink direction or the downlink direction,transparent-mode SDAP cannot be configured. As a result, additionalair-interface overheads and an effect on ROHC are caused. For example,an offset is made in a PDCP ROHC operation to avoid an SDAP header part.Therefore, in this embodiment of this application, unidirectionaltransparent-mode SDAP may be configured. To be specific, in thisembodiment of this application, unidirectional transparent-mode SDAP maybe configured in each of an uplink direction and a downlink direction ofa DRB. In other words, transparent-mode SDAP is configured in each ofthe uplink direction and the downlink direction of the DRB.

If an access-network network element determines to configuretransparent-mode SDAP in a downlink direction of at least one DRB, thatis, in the downlink direction of the at least one DRB, an SDAP PDUcarries no SDAP header, the access-network network element sends, to aterminal, indication information used to indicate configuration oftransparent-mode SDAP in the downlink direction of the DRB. For example,the access-network network element may send, to the terminal by usingRRC signaling or a user plane control PDU, the indication informationused to indicate the configuration of transparent-mode SDAP in thedownlink direction of the DRB.

For a DRB for which transparent-mode SDAP is configured in the downlinkdirection, a corresponding SDAP entity for sending the DRB in theaccess-network network element routes a data packet received from acore-network network element to the DRB without configuring an SDAPheader. In an ROHC compression processing process, a corresponding PDCPentity for sending the DRB in the access-network network element doesnot perform an initial compression location offset operation caused bythe SDAP header.

Further, in this embodiment of this application, the access-networknetwork element maps only a QoS flow whose reflective QoS and reflectivemapping are not activated to the DRB for which transparent-mode SDAP isconfigured.

For the DRB for which transparent-mode SDAP is configured in thedownlink direction, a corresponding SDAP entity for receiving the DRB inthe terminal does not read an SDAP header, and directly delivers a datapacket received from the DRB to an upper layer, such as a NAS layerprotocol entity. In an ROHC decompression processing process, acorresponding PDCP entity for receiving the DRB in the terminal does notperform an initial decompression location offset operation caused by theSDAP header.

If the access-network network element determines to configuretransparent-mode SDAP in an uplink direction of at least one DRB, thatis, in the uplink direction of the at least one DRB, an SDAP PDU carriesno SDAP header part, the access-network network element may send, to aterminal by using RRC or a user plane control PDU, indicationinformation used to indicate configuration of transparent-mode SDAP inthe uplink direction of the DRB.

The access-network network element maps, to the DRB for whichtransparent-mode SDAP is configured in the uplink direction, only anuplink QoS flow that does not need to carry a QoS flow ID.

For the DRB for which transparent-mode SDAP is configured in the uplink,a corresponding SDAP entity for sending the DRB in the terminal deliversa data packet received from a NAS layer to the DRB without configuringan SDAP header. In an ROHC compression processing process, acorresponding PDCP entity for sending the DRB in the terminal does notperform an initial compression location offset operation caused by theSDAP header. A corresponding SDAP entity for receiving the DRB in theaccess-network network element does not read an SDAP header. In an ROHCdecompression processing process, a corresponding PDCP entity forreceiving the DRB in the access-network network element does not performan initial decompression location offset operation caused by the SDAPheader.

In this embodiment of this application, after a transparent mode or anon-transparent mode is configured for an SDAP frame format, in a datatransmission process, the access-network network element may send SDAPmode information to the terminal. The SDAP mode information is used toindicate whether an SDAP frame format is in a transparent mode or anon-transparent mode, and indicate a direction corresponding to an SDAPmode. Further, non-transparent-mode SDAP may be further classified intotwo sub-modes: An SDAP PDU protocol header has a fixed length, or theSDAP PDU protocol header has a variable length.

The direction corresponding to the SDAP mode is an uplink direction or adownlink direction, or both. Further, no specific direction informationmay be carried in the SDAP mode information, so as to indicate that thecorresponding direction is bidirectional.

Further, the SDAP mode information may be configured in an explicitmanner or an implicit manner. For example, an explicit SDAP mode isconfigured for some DRBs or some directions of some DRBs, and anotherSDAP mode is configured in the remaining directions of the remainingDRBs or in all directions of the remaining DRBs.

A notification message format is that the SDAP mode information isincluded in a configuration message of a DRB. For example, theconfiguration message of the DRB may be configured in the followingmanners.

In a possible design:

 DRB list//Description: One or more DRBs may be included;  {DRBID//Description: an identifier of a DRB;  SDAP mode//Description: anSDAP mode;  Direction//Description: a direction corresponding to an SDAPmode: an uplink direction, a downlink direction, or both uplink anddownlink directions;  }  In another possible design:  An SDAP modeconfiguration includes an identifier of a DRB to indicate SDAP modeconfiguration of the DRB:  SDAP list{  {SDAP ID//Description: anidentifier of an SDAP entity;  SDAP mode 1//Description: an SDAP mode,such as a transparent mode; and a direction corresponding to the mode,such as a downlink direction, may be further included;  {DRB IDlist//Description: a list of DRB identifiers;  }  SDAP mode2//Description: an SDAP mode, such as a transparent mode; and adirection corresponding to the mode, such as an uplink direction, may befurther included;  {DRB ID list//Description: a list of DRB identifiers; }  SDAP mode 2//Description: an SDAP mode, such as a non-transparentmode; and a direction corresponding to the mode, such as an uplinkdirection, may be further included;  {DRB ID list//Description: a listof DRB identifiers;  }  }

Further, the access-network network element may configure an SDAP modebased on a granularity of a PDU session. To be specific, theaccess-network network element may configure an SDAP mode of a DRB for aPDU session. In other words, if only one SDAP mode is configured in anuplink direction, a downlink direction, or both uplink and downlinkdirections of an SDAP entity, the SDAP entity uses this SDAP mode forall DRBs corresponding to the PDU session.

Further, in a cell handover process of the terminal, a sourceaccess-network network element (a source base station) may send, to atarget access-network network element (a target base station), SDAP modeinformation corresponding to a DRB, so that the target access-networknetwork element (the target base station) may consider the SDAP modeinformation of the data packet in the following processing processes:determining an SDAP PDU format, determining whether to perform aninitial location offset operation during decompression processing forROHC compression, determining a mapping relationship between a QoS flowand a DRB, and so on.

In a possible design, when the source base station determines to handover the terminal to a target cell of the target base station, thesource base station sends a handover request message 1 to the targetbase station, and includes, in the handover request message 1, SDAP modeinformation of a DRB of the terminal. The SDAP mode information isconfigured for the terminal by the source base station in a source cell.The handover request message 1 may be sent by using a direct interfaceor an indirect interface between the base stations. The target basestation receives the handover request message 1 from the source basestation, and may reference the SDAP mode information, included in thehandover request message 1, of the DRB of the terminal when performingone or more of the following operations: determining an SDAP PDU format,determining whether to perform an initial location offset operationduring decompression processing for ROHC compression, determining amapping relationship between a QoS flow and a DRB, and so on. Forexample, when a mapping relationship between a QoS flow and a DRB isconfigured in the target cell, a QoS flow that does not need to carry aQoS flow ID through an air interface may be mapped to a DRB for whichtransparent-mode SDAP is configured. Further, the target base stationmay update a DRB configuration, for example, update an SDAP modeconfiguration of the DRB based on the SDAP mode information, included inthe handover request message 1, of the DRB of the terminal. Further, thetarget base station includes, in a handover request acknowledgmentmessage 2, SDAP mode information that is of the DRB of the terminal andthat is in the target cell.

After receiving the handover request message, the target base stationmay send the handover request acknowledgment message 2. The target basestation may send the handover request acknowledgment message 2 by usingthe direct interface or the indirect interface between the basestations. The source base station receives the handover requestacknowledgment message 2, and then sends a handover command message 3 tothe terminal. The terminal receives the handover command, and accessesthe target cell.

Further, SDAP mode information may also be transferred in amulti-connection offloading scenario. The multi-connection offloadingscenario means that the terminal accesses a communications network suchas a 5G network by using a master gNB (MgNB) and a secondary gNB (SgNB).The terminal may receive user plane data from a core network by usingthe master gNB or the secondary gNB. The terminal may also send data tothe core network by using the master gNB or the secondary gNB.

In a QoS flow migration process, the master gNB may migrate a QoS flowfrom the master gNB to the secondary gNB, or from the secondary gNB tothe master gNB. The master gNB may notify the secondary gNB of SDAP modeinformation of a DRB corresponding to a to-be-migrated QoS flow of theterminal. The secondary gNB may consider the SDAP mode information ofthe DRB during the following processing: determining an SDAP PDU format,determining whether to perform an initial location offset operationduring decompression processing for ROHC compression, determining amapping relationship between a QoS flow and a DRB, and so on. The mastergNB determines to migrate some QoS flows of the terminal to thesecondary gNB, and the master gNB sends a QoS flow migration requestmessage 1, and includes, in the QoS flow migration request message 1,the SDAP mode information of the DRB of the terminal. The SDAP modeinformation is configured by the master gNB for the terminal. The QoSflow migration means migrating a QoS flow from the master gNB to thesecondary gNB for sending or for offloading in the secondary gNB. Theoffloading in the secondary gNB means offloading a downlink data packetfrom the secondary gNB to the master gNB. The terminal receives data inthe master gNB and the secondary gNB. The terminal sends data to themaster gNB and secondary gNB in an uplink direction, and the secondarygNB receives data from the terminal and the master gNB, and sends thedata to a core network user plane device. The master gNB may send theQoS flow migration request message 1 to the secondary gNB by using amessage that includes but is not limited to an SGNB addition requestmessage, an SGNB modification request message, or the like. All QoSflows mapped to a DRB may be migrated, or some QoS flows mapped to a DRBmay be migrated.

The secondary gNB receives the QoS flow migration request message 1 fromthe master gNB, and sends a QoS flow migration request message 2. Thesecondary gNB may reference the SDAP mode information, included in theQoS flow migration request message 1, of the DRB of the terminal whenperforming one or more of the following operations: determining an SDAPPDU format, determining whether to perform an initial location offsetoperation during decompression processing for ROHC compression,determining a mapping relationship between a QoS flow and a DRB, and soon. For example, when a mapping relationship between a QoS flow and aDRB is configured in the secondary gNB, a QoS flow that does not need tocarry a QoS flow ID through an air interface may be mapped to a DRB forwhich transparent-mode SDAP is configured. Further, the secondary gNBmay update a DRB configuration, for example, update an SDAP modeconfiguration of the DRB based on the SDAP mode information, included inthe QoS flow migration request message 1, of the DRB of the terminal.Further, the master gNB includes, in the QoS flow migration requestacknowledgment message 2, SDAP mode information that is of the DRB ofthe terminal and that is in the secondary gNB. The terminal receivesdata, of the downlink QoS flow, sent by the secondary gNB or dataoffloaded from the secondary gNB. The terminal sends, in the secondarygNB, data of an uplink QoS flow.

Likewise, when the secondary gNB migrates a QoS flow to the master gNB,the secondary gNB may notify the master gNB of SDAP mode information ofa DRB corresponding to a to-be-migrated QoS flow of the terminal.

In still another embodiment of this application, a core-network networkelement may set a public QoS profile at a PDU session level. The publicQoS profile includes at least one of the following parameters: aresource type, a priority, a packet delay, a packet error rate, anallocation and retention priority, or the like. The resource typeincludes a guaranteed bit rate (GBR) or a non-GBR (Non-GBR).

In a process of establishing and modifying a PDU session, thecore-network network element sends a public QoS profile of the PDUsession to an access-network network element. For example, thecore-network network element may send the public QoS profile of the PDUsession to the access-network network element through an N2 interface byusing a message that includes but is not limited to a PDU SessionResource Setup message, a PDU Session Resource Modify message, or thelike. When establishing a default DRB of the PDU session, theaccess-network network element configures a parameter of the default DRBbased on the public QoS profile, for example, a PDCP layer parametercorresponding to the DRB, an RLC layer parameter corresponding to theDRB, or the like. The access-network network element may accept PDUsession establishment based on the public QoS profile of the PDUsession. If the access-network network element can accept the PDUsession establishment, the access-network network element accepts a PDUsession establishment request; or if the access-network network elementcannot accept the PDU session establishment, the access-network networkelement refuses to establish the PDU session.

If a public QoS profile of a PDU session is modified, the access-networknetwork element modifies, based on content of the public QoS profile, aparameter of a default DRB corresponding to the PDU session. Theaccess-network network element may accept PDU session establishmentbased on the public QoS profile of the PDU session. If theaccess-network network element can accept the PDU session establishment,the access-network network element accepts a PDU session establishmentrequest; or if the access-network network element cannot accept the PDUsession establishment, the access-network network element refuses toestablish the PDU session.

Further, in a cell handover process of the terminal, the access-networknetwork element may send a public QoS profile of a PDU session to atarget access-network network element, for example, send the public QoSprofile of the PDU session in a handover request message.

The target access-network network element receives the public QoSprofile of the PDU session, and establishes, based on content of the QoSprofile, a default DRB corresponding to the PDU session. The targetaccess-network network element may accept PDU session establishmentbased on the public QoS profile of the PDU session. If the targetaccess-network network element can accept the PDU session establishment,the target access-network network element accepts a PDU sessionestablishment request; or if the target access-network network elementcannot accept the PDU session establishment, the target access-networknetwork element refuses to establish the PDU session.

In a data offloading architecture, when a master access-network networkelement (such as a master gNB) determines to migrate a PDU session orsome QoS flows in a PDU session to a secondary access-network networkelement (such as a second gNB), the master access-network networkelement sends a public QoS profile of the PDU session to the secondaryaccess-network network element. The master access-network networkelement may use a message that includes but is not limited to an SGNBaddition request (SGNB addition request) message, an SGNB modificationrequest message, or the like. The secondary access-network networkelement may configure a parameter of a default DRB based on the publicQoS profile of the PDU session, and may further accept PDU sessionestablishment based on the public QoS profile of the PDU session.

In this embodiment of this application, an implementation in which thecore-network network element may set a public QoS profile at a PDUsession level may be applied to a secondary cell load (second cell groupbearer, SCG Bearer) scenario and a split load (split Bearer) scenario.

In still another embodiment of this application, optimization forin-order transmission of a data packet of a QoS flow is provided. Acore-network network element notifies an access-network network elementof in-order transmission information of a QoS flow or a PDU session. Thein-order transmission information means whether packets of the QoS flowor the PDU session need to be transmitted in order. A core networkcontrol plane network element may notify the access-network networkelement of the in-order transmission information of the QoS flow or thePDU session by using an N2 interface message. The used N2 interfacemessage includes but is not limited to a PDU Session Resource Setupmessage, a PDU Session Resource Modify message, or the like. Further,the core-network network element may notify a terminal of the in-ordertransmission information of the QoS flow or the PDU session, forexample, by using a NAS layer message. The QoS flow includes an uplinkQoS flow or a downlink QoS flow.

Further, a core network user plane network element may notify a RAN ofthe in-order transmission information of the QoS flow or the PDU sessionthrough an N3 interface. For example, the core network user planenetwork element adds, to an encapsulation header of a data packet at theN3 interface, indication information used to indicate whether the datapacket needs to be transmitted in order.

Considering in-order transmission information of a data packet,specifically, the RAN mainly uses the following manners to transmit adata packet through an air interface.

Implementation 1 of the RAN: A QoS flow is mapped to a DRB based onin-order transmission information.

The RAN may map a QoS flow to a DRB based on in-order transmissioninformation of a QoS flow or a PDU session. The RAN may map, to a sameDRB, QoS flows that do not need to be transmitted in order. To bespecific, none of data in the DRB needs to be transmitted in order. Forexample, the RAN maps, to a same DRB, a plurality of QoS flows that havea same QoS parameter or similar QoS parameters and that do not need tobe transmitted in order. Alternatively, the RAN maps, to a same DRB, QoSflows that need to be transmitted in order. To be specific, all data inthe DRB needs to be transmitted in order.

For an uplink, a base station notifies the terminal of a mappingrelationship between a QoS flow and a DRB. Further, the base stationnotifies the terminal that data in a DRB needs to be transmitted out oforder. For example, the base station notifies the terminal by using anRRC message or a user plane control PDU. The terminal may performoptimization processing when sending the data in the DRB.

For a downlink, if the base station notifies the terminal that data in aDRB needs to be transmitted out of order, a PDCP layer entity, in theterminal, that corresponds to the DRB does not need to perform a sortingoperation, and the PDCP layer protocol entity can directly deliver adata packet received from an RLC layer to an upper-layer protocolwithout performing a sorting operation on the data packet.

In this manner, different processing may be performed between the basestation and the terminal based on an in-order transmission requirementof a DRB, and a PDCP layer may not perform a sorting operation on a DRBthat needs to be transmitted out of order, so as to improve processingefficiency.

Implementation 2 of the RAN: In-order transmission information is notconsidered for mapping a QoS flow to a DRB.

In this scenario, a DRB may include data packets that need to betransmitted in order and data packets that do not need to be transmittedin order.

For Implementation 2 of the RAN, this application provides threetechnical solutions that are separately described below.

Solution 1: Indication information is added to an SDAP header.

An SDAP entity at a transmit end obtains in-order transmissioninformation of a packet, and adds indication information to an SDAPheader, so as to indicate whether the packet needs to be transmitted inorder. An SDAP PDU is sent to a receive end after being processed at aPDCP layer, an RLC layer, a MAC layer, a physical layer, or the like. APDCP layer entity at the receive end reads the SDAP header of thereceived PDCP SDU, and learns the in-order transmission informationbased on the indication information in the SDAP header. If the datapacket needs to be transmitted out of order, the PDCP layer entitydirectly delivers the data packet to an upper layer; or if the datapacket needs to be transmitted in order, the PDCP layer entity sorts thePDCP SDU based on a PDCP SN, and sequentially delivers the data packetto an upper layer after the data packet is sorted. In another manner,the PDCP layer entity reads an SDAP header of only a PDCP SDU receivedout of order, to learn the in-order transmission information.

For example, the PDCP receives a data packet 1, a data packet 3, and adata packet 5. If the data packet 3 does not need to be delivered inorder, the PDCP layer entity delivers the data packet 1 and the datapacket 3 to the upper layer, and makes a record indicating that the datapacket 3 has been delivered to the upper layer. The PDCP entity storesthe data packet 5 at a PDCP layer, and when the PDCP entity receives adata packet 2 and a data packet 4, and the data packet 2 and the datapacket 4 both need to be delivered in order, the PDCP entity deliversthe data packet 2, the data packet 4, and the data packet 5 to an upperlayer. The PDCP layer may read SDAP headers of only the data packet 3and the data packet 5 that are out of order, to learn in-ordertransmission information.

This solution may be applied to uplink and downlink directions.

Solution 2: Indication information is added to a PDCP layer protocolheader.

An SDAP entity at a transmit end obtains in-order transmissioninformation of a packet, and notifies a PDCP layer of the in-ordertransmission information of the data packet by using an SDAP layerprimitive and a PDCP layer primitive. A PDCP layer entity addsindication information to a PDCP layer protocol header, to indicatewhether the data packet needs to be transmitted in order. A PDCP PDU issent to a receive end after being processed at an RLC layer, a MAClayer, a physical layer, or the like. A PDCP layer entity at the receiveend reads the PDCP layer protocol header of the received PDCP SDU, tolearn the in-order transmission information. If the data packet needs tobe transmitted out of order, the PDCP layer entity directly delivers thedata packet to an upper layer; or if the data packet needs to betransmitted in order, the PDCP layer entity sorts the PDCP SDU based ona PDCP SN, and sequentially delivers the data packet to an upper layerafter the data packet is sorted. In another manner, the PDCP layerentity reads a PDCP protocol header of only a PDCP SDU received out oforder, to learn the in-order transmission information.

For example, the PDCP receives a data packet 1, a data packet 3, and adata packet 5. If the data packet 3 does not need to be delivered inorder, the PDCP layer entity delivers the data packet 1 and the datapacket 3 to the upper layer, and makes a record indicating that the datapacket 3 has been delivered to the upper layer. The PDCP entity storesthe data packet 5 at a PDCP layer, and when the PDCP entity receives adata packet 2 and a data packet 4, and the data packet 2 and the datapacket 4 both need to be delivered in order, the PDCP entity deliversthe data packet 2, the data packet 4, and the data packet 5 to an upperlayer. The PDCP layer may read PDCP protocol headers of only the datapacket 3 and the data packet 5 that are out of order, to learn in-ordertransmission information; or read partial content of a PDCP layerprotocol header, such as in-order transmission indication information.

This solution may be applied to uplink and downlink directions.

Solution 3: A PDCP entity at a receive end reads a QoS flow ID at anSDAP layer.

An SDAP entity at a transmit end adds a QoS flow ID to an SDAP header,and a PDCP PDU is sent to a receive end after being processed at an RLClayer, a MAC layer, a physical layer, or the like. A PDCP layer entityat the receive end reads an SDAP layer protocol header part of thereceived PDCP SDU, to learn the QoS flow ID, and learns in-ordertransmission information of a data packet based on in-order transmissioninformation that is of a QoS flow and that is notified by thecore-network network element to the RAN. If the data packet needs to betransmitted out of order, the PDCP layer entity directly delivers thedata packet to an upper layer; or if the data packet needs to betransmitted in order, the PDCP layer entity sorts the PDCP SDU based ona PDCP SN, and sequentially delivers the data packet to an upper layerafter the data packet is sorted. In another manner, the PDCP layerentity reads an SDAP layer protocol header of only a PDCP SDU receivedout of order, and reads a QoS flow ID from the SDAP layer protocolheader, to learn in-order transmission information.

For example, the PDCP layer receives a data packet 1, a data packet 3,and a data packet 5. If the data packet 3 does not need to be deliveredin order, the PDCP layer entity delivers the data packet 1 and the datapacket 3 to the upper layer, and makes a record indicating that the datapacket 3 has been delivered to the upper layer. The PDCP entity storesthe data packet 5 at a PDCP layer, and when the PDCP entity receives adata packet 2 and a data packet 4, and the data packet 2 and the datapacket 4 both need to be delivered in order, the PDCP entity deliversthe data packet 2, the data packet 4, and the data packet 5 to an upperlayer. The PDCP layer may read SDAP layer protocol headers of only thedata packet 3 and the data packet 5 that are out of order, and reads aQoS flow ID to learn in-order transmission information.

This solution may be applied to an uplink direction.

In this manner, different processing may be performed between the basestation and the terminal based on in-order transmission requirements ofdifferent data packets in a DRB, and the PDCP layer may not perform asorting operation on a data packet that does not need to be transmittedin order, so as to improve processing efficiency. The PDCP layerperforms a sorting operation on a data packet that needs to betransmitted in order, so as to ensure in-order transmission requirementof a service.

In a possible implementation of this application, if cell handover forthe terminal occurs, a source access-network network element (a sourcebase station) that obtains the reflective QoS information may send theobtained reflective QoS information to a target access-network networkelement (a target base station) to which the terminal is to be handedover. The source access-network network element may send the reflectiveQoS information to the target access-network network element by using ahandover request message, and the target access-network network elementperforms steps in the foregoing embodiment that are related to theaccess-network network element. For example, the target access-networknetwork element may receive the reflective QoS information sent by thesource access-network network element, and performs one or more of thefollowing operations based on the reflective QoS information:determining whether to send a QoS flow ID through an air interface,configuring whether the terminal needs to read a QoS flow ID,configuring, for the terminal, a manner of configuring a mappingrelationship between a QoS flow and a DRB, determining whether toconfigure an SDAP entity for a PDU session, and so on.

Further, in a multi-connection scenario, an MgNB determines to migratesome QoS flows to an SgNB. The MgNB sends reflective QoS information ofthe QoS flows to the SgNB. For example, the MgNB sends the reflectiveQoS information of the QoS flows by using a message such as an SGNBaddition request message or an SGNB modification request (SGNBMODIFICATION REQUEST) message, so that the SgNB may perform one or moreof the following operations based on the reflective QoS information:determining whether to send a QoS flow ID through an air interface,configuring whether the terminal needs to read a QoS flow ID,configuring, for the terminal, a manner of configuring a mappingrelationship between a QoS flow and a DRB, determining whether toconfigure an SDAP entity for a PDU session, and so on.

Only functions of the SDAP protocol and the PDCP protocol in thisembodiment of this application are described, and any protocol layernames corresponding to the same functions are included.

It should be noted that, in the specification, claims, and accompanyingdrawings of this application, the terms “first”, “second”, and the likeare intended to distinguish between similar objects but do notnecessarily indicate a specific order or sequence. For example, thefirst indication information and the second indication information inthe embodiments of this application are merely for ease of descriptionand distinguishing between different indication information, and are notintended to limit the indication information. It should be understoodthat the data termed in such a way is interchangeable in propercircumstances so that the embodiments of this application describedherein can be implemented in other orders than the order illustrated ordescribed herein.

The foregoing describes the solutions provided in the embodiments ofthis application mainly from a perspective of a terminal, anaccess-network network element, and a core-network network element. Itmay be understood that to implement the foregoing functions, theterminal, the access-network network element, and the core-networknetwork element include corresponding hardware structures and/orsoftware structures for performing the functions. With reference tounits and algorithm steps of each example described in the embodimentsdisclosed in this application, the embodiments of this application maybe implemented in a form of hardware or a combination of hardware andcomputer software. Whether a function is performed by hardware orhardware driven by computer software depends on particular applicationsand design constraint conditions of the technical solutions. A personskilled in the art may use different methods to implement the describedfunctions for each particular application, but it should not beconsidered that the implementation goes beyond the scope of thetechnical solutions of the embodiments of this application.

In the embodiments of this application, the terminal, the access-networknetwork element, and the core-network network element may be dividedinto functional units according to the foregoing method examples. Forexample, a functional unit corresponding to each function may beobtained through division, or two or more functions may be integratedinto one processing unit. The integrated unit may be implemented in aform of hardware, or may be implemented in a form of a softwarefunctional unit. It should be noted that the unit division in theembodiments of this application is an example, and is merely logicalfunction division and may be another division manner in an actualimplementation.

Based on the foregoing methods, when an integrated unit is used, FIG. 20is a schematic structural diagram of a reflective QoScharacteristic-based communications apparatus 100 according to anembodiment of this application. The reflective QoS characteristic-basedcommunications apparatus 100 may correspond to the access-networknetwork element in the foregoing methods. Referring to FIG. 20, thereflective QoS characteristic-based communications apparatus 100includes a receiving unit 101 and a processing unit 102. The reflectiveQoS characteristic-based communications apparatus 100 may furtherinclude a transmitting unit 103.

Functions of the receiving unit 101, the processing unit 102, and thetransmitting unit 103 may correspond to the foregoing method steps, anddetails are not described herein again.

When a form of hardware is used for implementation, the receiving unit101 may be a receiver, a communications interface, and a transceivercircuit, the processing unit 102 may be a processor or a controller, andthe transmitting unit 103 may be a transmitter, a communicationsinterface, and a transceiver circuit. The communications interface is ageneral term, and may include one or more interfaces.

Based on the foregoing methods, FIG. 21 shows another schematicstructural diagram of the reflective QoS characteristic-basedcommunications apparatus 100 according to an embodiment of thisapplication. The reflective QoS characteristic-based communicationsapparatus may correspond to the access-network network element in theforegoing methods. The access-network network element may be a basestation or another device, and this is not limited herein.

Referring to FIG. 21, an access-network network element 1000 includes aprocessor 1001, a memory 1002, a bus system 1003, a receiver 1004, and atransmitter 1005. The processor 1001, the memory 1002, the receiver1004, and the transmitter 1005 are connected to each other by using thebus system 1003. The memory 1002 is configured to store an instruction.The processor 1001 is configured to execute the instruction stored inthe memory 1002, to control the receiver 1004 to receive a signal andcontrol the transmitter 1005 to send a signal, so as to complete stepsof the access-network network element in the foregoing methods. Thereceiver 1004 and the transmitter 1005 may be a same physical entity ordifferent physical entities. When the receiver 1004 and the transmitter1005 are a same physical entity, the receiver 1004 and the transmitter1005 may be collectively referred to as a transceiver. The memory 1002may be integrated into the processor 1001, or may be separated from theprocessor 1001.

In an implementation, functions of the receiver 1004 and the transmitter1005 may be implemented by using a transceiver circuit or a dedicatedchip. The processor 1001 may be implemented by using a dedicatedprocessing chip, a processing circuit, a processor, or a universal chip.

In another implementation, a general-purpose computer may be consideredto implement the access-network network element provided in thisembodiment of this application. To be specific, program code forimplementing functions of the processor 1001, the receiver 1004, and thetransmitter 1005 is stored in the memory. A general-purpose processorexecutes the code in the memory to implement the functions of theprocessor 1001, the receiver 1004, and the transmitter 1005.

For concepts, explanations, detailed descriptions, and other steps thatare related to the reflective QoS characteristic-based communicationsapparatus 100 and the access-network network element 1000, refer todescriptions about the content in the foregoing methods or in anotherembodiment. Details are not described herein again.

Based on the foregoing methods, when an integrated unit is used, FIG. 22shows a schematic structural diagram of a reflective QoScharacteristic-based communications apparatus 200 according to anembodiment of this application. The reflective QoS characteristic-basedcommunications apparatus 200 may correspond to the core-network networkelement in the foregoing methods. Referring to FIG. 22, the reflectiveQoS characteristic-based communications apparatus 200 includes aprocessing unit 201 and a transmitting unit 202. Functions of theprocessing unit 201 and the transmitting unit 202 may correspond to theforegoing method steps, and details are not described herein again.

When a form of hardware is used for implementation, the processing unit201 may be a processor or a controller, and the transmitting unit 202may be a transmitter, a communications interface, and a transceivercircuit. The communications interface is a general term, and may includeone or more interfaces.

Based on the foregoing methods, FIG. 23 shows another schematicstructural diagram of the reflective QoS characteristic-basedcommunications apparatus 200 according to an embodiment of thisapplication. The reflective QoS characteristic-based communicationsapparatus may correspond to the core-network network element in theforegoing methods. The core-network network element may be an AMF, aUMF, or another device, and this is not limited herein.

Referring to FIG. 23, a core-network network element 2000 includes aprocessor 2001, a memory 2002, a bus system 2003, and a transmitter2004. The processor 2001, the memory 2002, and the transmitter 2004 areconnected to each other by using the bus system 2003. The memory 2002 isconfigured to store an instruction. The processor 2001 is configured toexecute the instruction stored in the memory 2002, to control thetransmitter 2004 to send a signal, so as to complete steps of thecore-network network element in the foregoing methods. The transmitter2004 may be collectively referred to as a transceiver. The memory 2002may be integrated into the processor 2001, or may be separated from theprocessor 2001.

In an implementation, a function of the receiver 2004 may be implementedby using a transceiver circuit or a dedicated chip. The processor 2001may be implemented by using a dedicated processing chip, a processingcircuit, a processor, or a universal chip.

In another implementation, a general-purpose computer may be consideredto implement the core-network network element provided in thisembodiment of this application. To be specific, program code forimplementing functions of the processor 2001 and the transmitter 2004 isstored in the memory. A general-purpose processor executes the code inthe memory to implement the functions of the processor 2001 and thetransmitter 2004.

For concepts, explanations, detailed descriptions, and other steps thatare related to the reflective QoS characteristic-based communicationsapparatus 200 and the core-network network element 2000, refer todescriptions about the content in the foregoing methods or in anotherembodiment. Details are not described herein again.

Based on the foregoing methods, when an integrated unit is used, FIG. 24shows a schematic structural diagram of a reflective QoScharacteristic-based communications apparatus 300 according to anembodiment of this application. The reflective QoS characteristic-basedcommunications apparatus 300 may correspond to the terminal in theforegoing methods. Referring to FIG. 24, the reflective QoScharacteristic-based communications apparatus 300 includes a receivingunit 301 and a processing unit 302. Functions of the receiving unit 301and the processing unit 302 may correspond to the foregoing methodsteps, and details are not described herein again.

When a form of hardware is used for implementation, the processing unit302 may be a processor or a controller, and the receiving unit 301 maybe a receiver, a communications interface, and a transceiver circuit.The communications interface is a general term, and may include one ormore interfaces.

Based on the foregoing methods, FIG. 25 shows another schematicstructural diagram of the reflective QoS characteristic-basedcommunications apparatus 300 according to an embodiment of thisapplication. The reflective QoS characteristic-based communicationsapparatus 300 may correspond to the terminal in the foregoing methods.

Referring to FIG. 25, a terminal 3000 may include a transmitter 3001, areceiver 3002, a processor 3003, and a memory 3004. Further, theterminal 3000 may include an antenna 3005. The transmitter 3001, thereceiver 3002, the processor 3003, and the memory 3004 may be connectedto each other by using a bus system. The memory 3004 is configured tostore an instruction. The processor 3003 is configured to execute theinstruction stored in the memory 3004, to control the receiver 3002 toreceive a signal and control the transmitter 3001 to send a signal, soas to complete steps of the terminal in the foregoing methods. Thereceiver 3002 and the transmitter 3001 may be a same physical entity ordifferent physical entities. When the receiver 3002 and the transmitter3001 are a same physical entity, the receiver 3002 and the transmitter3001 may be collectively referred to as a transceiver. The memory 3004may be integrated into the processor 3003, or may be separated from theprocessor 3003.

In an implementation, functions of the receiver 3002 and the transmitter3001 may be implemented by using a transceiver circuit or a dedicatedchip. The processor 3003 may be implemented by using a dedicatedprocessing chip, a processing circuit, a processor, or a universal chip.

In another implementation, a general-purpose computer may be consideredto implement the terminal provided in this embodiment of thisapplication. To be specific, program code for implementing functions ofthe processor 3003, the receiver 3002, and the transmitter 3001 isstored in the memory. A general-purpose processor executes the code inthe memory to implement the functions of the processor 3003, thereceiver 3002, and the transmitter 3001.

For concepts, explanations, detailed descriptions, and other steps thatare related to the reflective QoS characteristic-based communicationsapparatus 300 and the terminal 3000, refer to descriptions about thecontent in the foregoing methods or in another embodiment. Details arenot described herein again.

Based on the methods provided in the embodiments of this application, anembodiment of this application further provides a communications system,and the communications system includes the foregoing access-networknetwork element and core-network network element, and one or moreterminals.

Based on the methods provided in the embodiments of this application, anembodiment of this application further provides a computer storagemedium, configured to store some instructions. When these instructionsare executed, any method related to the terminal, the access-networknetwork element, or the core-network network element may be completed.

Based on the methods provided in the embodiments of this application, anembodiment of this application further provides a computer programproduct, configured to store a computer program. The computer program isused to perform the reflective QoS characteristic-based communicationsmethods in the foregoing method embodiments.

It should be understood that in the embodiments of this application, theprocessor may be a central processing unit (CPU), or the processor maybe another general-purpose processor, a digital signal processor (DSP),an application-specific integrated circuit (ASIC), a field programmablegate array (FPGA), another programmable logic device, discrete gate ortransistor logic device, discrete hardware component, or the like. Thegeneral-purpose processor may be a microprocessor, or the processor maybe any conventional processor or the like.

The memory may include a read-only memory and a random access memory,and provide an instruction and data to the processor 310. A part of thememory may further include a non-volatile random access memory. Forexample, the memory may further store information of a device type.

The bus system may include a power bus, a control bus, a status signalbus, and the like in addition to a data bus. However, for cleardescription, various types of buses in the figures are marked as the bussystem.

In an implementation process, steps in the foregoing methods can beimplemented by using a hardware integrated logical circuit in theprocessor, or by using instructions in a form of software. The steps ofthe methods disclosed with reference to the embodiments of thisapplication may be directly performed by a hardware processor, or may beperformed by using a combination of hardware in the processor and asoftware module. The software module may be located in a mature storagemedium in the art, such as a random access memory, a flash memory, aread-only memory, a programmable read-only memory, an electricallyerasable programmable memory, a register, or the like. The storagemedium is located in the memory, and a processor reads information inthe memory and completes the steps in the foregoing methods incombination with hardware of the processor. To avoid repetition, detailsare not described herein again.

It should be understood that sequence numbers of the foregoing processesdo not mean execution sequences in various embodiments of thisapplication. The execution sequences of the processes should bedetermined according to functions and internal logic of the processes,and should not be construed as any limitation on the implementationprocesses of the embodiments of this application.

A person of ordinary skill in the art may be aware that, in combinationwith the examples described in the embodiments disclosed in thisapplication, units and algorithm steps may be implemented by electronichardware or a combination of computer software and electronic hardware.Whether the functions are performed by hardware or software depends onparticular applications and design constraint conditions of thetechnical solutions. A person skilled in the art may use differentmethods to implement the described functions for each particularapplication, but it should not be considered that the implementationgoes beyond the scope of this application.

It may be clearly understood by a person skilled in the art that, forthe purpose of convenient and brief description, for a detailed workingprocess of the foregoing system, apparatus, and unit, reference may bemade to a corresponding process in the foregoing method embodiments, anddetails are not described herein again.

In the several embodiments provided in this application, it should beunderstood that the disclosed systems, apparatuses, and methods may beimplemented in other manners. For example, the described apparatusembodiments are merely examples. For example, the unit division ismerely logical function division and may be other division in actualimplementation. For example, a plurality of units or components may becombined or integrated into another system, or some features may beignored or not performed. In addition, the displayed or discussed mutualcouplings or direct couplings or communication connections may beimplemented by using some interfaces. The indirect couplings orcommunication connections between the apparatuses or units may beimplemented in electronic, mechanical, or other forms.

The units described as separate parts may or may not be physicallyseparate, and parts displayed as units may or may not be physical units,may be located in one position, or may be distributed on a plurality ofnetwork units. Some or all of the units may be selected according toactual requirements to achieve the objectives of the solutions of theembodiments.

In addition, functional units in the embodiments of this application maybe integrated into one processing unit, or each of the units may existalone physically, or two or more units are integrated into one unit.

When the functions are implemented in the form of a software functionalunit and sold or used as an independent product, the functions may bestored in a computer-readable storage medium. Based on such anunderstanding, the technical solutions of this application essentially,or the part contributing to the prior art, or some of the technicalsolutions may be implemented in a form of a software product. Thesoftware product is stored in a storage medium, and includes severalinstructions for instructing a computer device (which may be a personalcomputer, a server, a network device, or the like) to perform all orsome of the steps of the methods described in the embodiments of thisapplication. The foregoing storage medium includes: any medium that canstore program code, such as a USB flash drive, a removable hard disk, aread-only memory (ROM), a random access memory (RAM), a magnetic disk,or an optical disc.

The foregoing descriptions are merely specific implementations of thisapplication, but are not intended to limit the protection scope of thisapplication. Any variation or replacement readily figured out by aperson skilled in the art within the technical scope disclosed in thisapplication shall fall within the protection scope of this application.Therefore, the protection scope of this application shall be subject tothe protection scope of the claims

What is claimed is:
 1. A communication method, comprising: receiving, bya terminal, from a first access-network network element an identifier(ID) of a first data radio bearer (DRB) and information indicatingwhether to configure a Service Data Adaptation Protocol (SDAP) headerfor the first DRB; receiving, by the terminal, from a secondaccess-network network element information indicating whether toconfigure a SDAP header for a second DRB of the terminal and that is ina target cell; wherein the first access-network network element is asource access-network network element, the second access-network networkelement is a target access-network network element, the informationindicating whether to configure a SDAP header for a DRB of the terminaland that is in the target cell is determined by the secondaccess-network network element after receiving a handover requestmessage, the handover request message comprises the ID of the first DRBand the information indicating whether to configure the SDAP header forthe first DRB; or wherein the first access-network network element is amaster gNB or a secondary gNB, the second access-network network elementis a secondary gNB or a master gNB, the information indicating whetherto configure a SDAP header for a second DRB of the terminal and that isin the target cell is determined by the second access-network networkelement after receiving a QoS flow migration request message, the QoSflow migration request message comprises information indicating whetherto configure the SDAP header for the first DRB, the first DRB iscorresponding to a to-be-migrated QoS flow of the terminal.
 2. Thecommunication method according to claim 1, wherein the informationindicating whether to configure the SDAP header for the first DRBcomprises at least one of information indicating whether to configurethe SDAP header in an uplink direction of the first DRB, or informationindicating whether to configure the SDAP header in a downlink directionof the first DRB.
 3. The communication method according to claim 1,wherein the information indicating whether to configure the SDAP headerfor the second DRB comprises at least one of information indicatingwhether to configure the SDAP header in an uplink direction of thesecond DRB, or information indicating whether to configure the SDAPheader in a downlink direction of the second DRB.
 4. The communicationmethod according to claim 1, wherein the handover request messagefurther comprises reflective quality of service (reflective QoS)information.
 5. The communication method according to claim 1, whereinthe information indicating whether to configure the SDAP header for thefirst DRB is the information indicating configuring the SDAP header forthe first DRB, the method further comprises: receiving, by the terminal,from the first access-network network element a data packet, wherein aSDAP header of the data packet comprises a non-access stratum reflectiveQoS indicator field and an access stratum reflective mapping indicatorfield.
 6. The communication method according to claim 1, wherein theinformation indicating whether to configure the SDAP header for thefirst DRB is the information indicating not configuring the SDAP headerin an uplink direction for the first DRB, the method further comprises:the terminal does not perform an initial compression location offsetoperation caused by the SDAP header in an Robust Header Compression(ROHC) compression processing process.
 7. The communication methodaccording to claim 1, wherein the information indicating whether toconfigure the SDAP header for the first DRB is the informationindicating not configuring the SDAP header in an downlink direction forthe first DRB, the method further comprises: the terminal does notperform an initial compression location offset operation caused by theSDAP header in an Robust Header Compression (ROHC) compressionprocessing process.
 8. The communication method according to claim 1,wherein the information indicating whether to configure the SDAP headerfor the first DRB is the information indicating configuring the SDAPheader in a downlink direction for the first DRB, the method furthercomprises: making, by the terminal, an offset made in a PDCP ROHCoperation to avoid an SDAP header part.
 9. The communication methodaccording to claim 1, wherein the first DRB and the second DRB is a sameDRB.
 10. A communication method, comprising: receiving, by a terminal,from a source access-network network element an identifier (ID) of afirst data radio bearer (DRB) and information indicating whether toconfigure a Service Data Adaptation Protocol (SDAP) header for the firstDRB; receiving, by the terminal, from a source access-network networkelement a handover command message, the handover command messagecomprises information configured by a target cell and the informationindicating whether to configure a SDAP header for a second DRB of theterminal and that is in the target cell.
 11. A communication apparatus,comprising a receiver configured to: receive from a first access-networknetwork element an identifier (ID) of a first data radio bearer (DRB)and information indicating whether to configure a Service DataAdaptation Protocol (SDAP) header for the first DRB; receive from asecond access-network network element information indicating whether toconfigure a SDAP header for a second DRB of the communication apparatusand that is in a target cell; wherein the first access-network networkelement is a source access-network network element, the secondaccess-network network element is a target access-network networkelement, the information indicating whether to configure a SDAP headerfor a second DRB of the communication apparatus and that is in thetarget cell is determined by the second access-network network elementafter receiving a handover request message, the handover request messagecomprises the ID of the first DRB and the information indicating whetherto configure the SDAP header for the first DRB; or wherein the firstaccess-network network element is a master gNB or a secondary gNB, thesecond access-network network element is a secondary gNB or a mastergNB, the information indicating whether to configure a SDAP header for asecond DRB of the communication apparatus and that is in the target cellis determined by the second access-network network element afterreceiving a QoS flow migration request message, the QoS flow migrationrequest message comprises the information indicating whether toconfigure the SDAP header for the first DRB, the first DRB iscorresponding to a to-be-migrated QoS flow of the communicationapparatus.
 12. The communication apparatus according to claim 11,wherein the information indicating whether to configure the SDAP headerfor the first DRB comprises at least one of information indicatingwhether to configure the SDAP header in an uplink direction of the firstDRB, or information indicating whether to configure the SDAP header in adownlink direction of the first DRB.
 13. The communication apparatusaccording to claim 11, wherein the information indicating whether toconfigure the SDAP header for the second DRB comprises at least one ofinformation indicating whether to configure the SDAP header in an uplinkdirection of the second DRB, or information indicating whether toconfigure the SDAP header in a downlink direction of the second DRB. 14.The communication apparatus according to claim 11, wherein the handoverrequest message further comprises reflective quality of service(reflective QoS) information.
 15. The communication apparatus accordingto claim 11, wherein the information indicating whether to configure theSDAP header for the first DRB is the information indicating configuringthe SDAP header for the first DRB, the receiver is configured to:receiving from the first access-network network element a data packet,wherein a SDAP header of the data packet comprises a non-access stratumreflective QoS indicator field and an access stratum reflective mappingindicator field.
 16. The communication apparatus according to claim 11,wherein the information indicating whether to configure the SDAP headerfor the first DRB is the information indicating not configuring the SDAPheader in an uplink direction for the first DRB, the communicationapparatus does not perform an initial compression location offsetoperation caused by the SDAP header in an Robust Header Compression,ROHC, compression processing process.
 17. The communication apparatusaccording to claim 11, wherein the information indicating whether toconfigure the SDAP header for the first DRB is the informationindicating not configuring the SDAP header in an downlink direction forthe first DRB, the communication apparatus does not perform an initialcompression location offset operation caused by the SDAP header in anRobust Header Compression (ROHC) compression processing process.
 18. Thecommunication apparatus according to claim 11, wherein the informationindicating whether to configure the SDAP header for the first DRB is theinformation indicating configuring the SDAP header in a downlinkdirection for the first DRB, the communication apparatus makes an offsetmade in a PDCP ROHC operation to avoid an SDAP header part.
 19. Thecommunication apparatus according to claim 11, wherein the first DRB andthe second DRB is a same DRB.
 20. A communication apparatus, comprisinga receiver configured to: receive from a source access-network networkelement an identifier (ID) of a first data radio bearer (DRB) andinformation indicating whether to configure a Service Data AdaptationProtocol (SDAP) header for the first DRB; receive from the sourceaccess-network network element a handover command message, the handovercommand message comprises information configured by a target cell andinformation indicating whether to configure a SDAP header for a secondDRB of the communication apparatus and that is in the target cell.